Skip to content

Latest commit

 

History

History
19 lines (17 loc) · 2.65 KB

publishing.md

File metadata and controls

19 lines (17 loc) · 2.65 KB
Raw

The release process here mostly follows along with the vbump script that @indexzero wrote several years ago, but the main steps for a release are as follows:

  1. Complete merging in any PRs that should be part of the release.
  2. Update the changelog. Check to make sure you've caught everything using GitHub's compare tool (example here). It's nice to thank the contributors here. It's nice to organize this by which changes would merit which level of semver bump, and especially call out any breaking changes (major-version-number) concisely at the start.
  3. Update the version number in package.json and package-lock.json, bumping as appropriate for semver based on the most significant position change trigger from the changelog you just wrote/reviewed. Do not miss this step!
  4. Make sure your local master branch is up to date.
  5. Make sure all the lint checks and tests pass, beyond what the CI might've told you.
  6. On the Releases tab in the GitHub UI, click 'Draft a new release' in the upper right corner.
  7. Under the 'Choose a tag' dropdown, type the name of the new version starting with a v (e.g. v3.7.0) and don't forget to click the 'Create new tag on publish' option below (this step is annoyingly easy to miss): image
  8. Paste the same version number, with or without the v (with is probably better) in the release title box.
  9. Paste the contents of the changelog for this release in the 'Describe this release' box.
  10. Click "Publish release."
  11. Back on the command line, npm publish and complete npm 2FA as needed.
  12. Update the distribution tags, for example: npm dist-tag add [email protected] 3.x-latest.
  13. Verify the distribution tags look correct under the 'Versions' tab at https://www.npmjs.com/package/winston or with npm dist-tag ls.
  14. Keep a closer-than-usual eye on issues in the hours and days that follow, prepared to quickly revert/address anything that might be associated with that release.

A more professional version of this would probably use a release branch off master to make sure no other maintainers merge a PR into master between the loading of a compare view for changelog preparation and completion of the process, but we're such a small team that the extra steps are probably not needed. After release, you can also verify with the compare view between the new and prior release tags to see when the latest change was and verify it was before you started the process.