-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: include release artifacts & tags #264
Comments
Thanks for the suggestion @brettswift. I will look into these tools. For now only way to backtrack the sourcecode to npm version is to look for that commit in master that changed "version" field of package.json. And the changelog is actually the commit message of each commit in master. |
Thanks for the tip!
…On Tue., Oct. 6, 2020, 14:47 Nahiyan Kamal, ***@***.***> wrote:
Thanks for the suggestion @brettswift <https://github.com/brettswift>. I
will look into these tools.
For now only way to backtrack the sourcecode to npm version is to look for
that commit in master that changed "version" field of package.json. And the
changelog is actually the commit message of each commit in master.
This is not super friendly if you want to automate things but still
changes are backtrackable if its necessary.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#264 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFQYFJR4NAENOUYKCLXYC3SJN66JANCNFSM4SAQRWPQ>
.
|
@brettswift Added semantic release feature for deployment. Now you have:
NOTE |
That's awesome. Thanks!
…On Wed., Nov. 4, 2020, 05:26 Nahiyan Kamal, ***@***.***> wrote:
Closed #264 <#264>
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#264 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFQYFLQW3RMVTSW2CPZK73SOFB67ANCNFSM4SAQRWPQ>
.
|
Hi,
Thanks for writing this - we quite like it.
I noticed a bunch of new versions, but there isn't a changelog, nor tags on the repo mapping back to the NPM package.
Just some friendly feedback for users - it would be great if we could see a change log file or at least tags on the repo that match the npm artifacts. We actually use this in a cli app that we share with 50+ people so it would be nice to make the upgrade path a little easier.
I've found using commitizen and standard-version packages make this quite a nice experience - if you were looking for a suggestion.
Anyways, thanks again for publishing this!
The text was updated successfully, but these errors were encountered: