Repository navigation
Conversation
|
You can see an example of what the GitHub Releases end up looking like here https://github.com/webpro/release-it/releases. @modeswitch my thinking is to land this, and try doing a release, tweak things, repeat until I get it right. If you disagree, speak up! My personal view is that I can probably just do minor updates, since I've been able to not break 0.44 versions. However, tons has changed, so I could also do a major number update too. Let me know your thoughts. |
Codecov Report
@@ Coverage Diff @@
## master #640 +/- ##
=======================================
Coverage 86.62% 86.62%
=======================================
Files 16 16
Lines 1742 1742
=======================================
Hits 1509 1509
Misses 233 233Continue to review full report at Codecov.
|
|
Merged. |
Fixes #404 by modernizing our release process to use release-it. With the changes in this PR, one of @modeswitch or me (or whoever we give rights to), can do:
This will do a bunch of things automatically:
dist/package.jsonSee this post for a more verbose description. The tool is interactive by default, and will look something like this:
All default choices are defined in
.release-it.jsonbelow.I've included docs in
CONTRIBUTING.md, but to summarize what is important:env.sampleto.envand include aGITHUB_TOKENthey generate for themselves.npm loginso they can publish tonpmI haven't run this fully yet, so I may need to fix a few corner cases. We can do a few runs to get it right, then start using this.