Files: 55fc93a9190c25f467ead205ab8d676b5191dbd4 / docs / RELEASE_GUIDE.md
How to make a patchwork release
You will need
- To be a member of the
ssbc/patchwork
repository with push capabilities tomaster
- An npmjs.com account that's part of the ssbc, to publish the npm package
Steps
Check out
master
and make sure you're 100% up-to-date with origin.git fetch origin && git reset --hard origin/master
makes this pretty simple.npm version $whatever
, usually this will benpm version patch
ornpm version minor
but when doing a prerelease you have to donpm version prerelease --preid beta
. This is fine to do inmaster
IMO because it isn't changing any code.git push --tags origin master
should push your commit and the tag, which should set off Travis which will push a draft release. Look at the releases and you should see the draft.Wait for all of the builds to finish, it takes ~10 minutes for macOS and Linux but ~25 minutes for Windows. Then you'll edit the draft, change the title from "1.0.0" to "Patchwork v1.0.0" and set a body with the output of
npm run --silent release-notes
.If it's an alpha or beta make sure to tick the "this is a prerelease box" at the bottom, hit "preview" to make sure you haven't borked your Markdown, and then hit "publish" release.
Write up an announcement to publish on SSB. :)
Built with git-ssb-web