-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Automate releasing #539
Automate releasing #539
Conversation
I started doing something a long time ago but went nowhere cause I didn't finish it: https://github.com/js-cookie/js-cookie-release |
This will allow for easier, automated bumping during releasing.
This configuration supplies publishing to npm along with making a release on GitHub with additional assets to be uploaded (in particular minified versions for both the module and nonmodule variants).
@FagnerMartinsBrack I see... I came across release-it, and it seems rather powerful, and as far as I can see it does all we need for our automated release process. |
My concern with a third party release tool is that history tells (as of Java Maven, some Grunt packages, etc.) that there seems to be no tool that can generalize all release process steps for all projects. At some point, the projects end up having either too many configurations or missing features that force project authors to automate their own process using a higher level language (bash, some node scripts, etc.). In the case of I guess we'll only know in hindsight 😆 |
This doesn't seem to provide value. We may have to craft release notes manually for a GitHub release (thus we keep creating the release as a draft).
Should we introduce a (Probably doesn't matter much, we won't be releasing all the time, with many changes..?!) |
So far |
PS: And to me it's an improvement over a manual process in any case. Sorry for not picking up the work that had once been started on this. |
I'm glad you didn't. I'm not even sure that effort would give a meaningful ROI anyway |
Don't forget to move the |
Another part of the ongoing effort of modernizing the codebase. Since we now need to provide different variants/distributions of the library (module/nonmodule including minified versions), we aim for fully automating publishing to npm, as to avoid errors during the process.
We start using release-it for fully automating both publishing to npm as well as creating releases on GitHub. Those GitHub releases do contain the minified sources, thus we're able to address #501.