Release steps

  1. create a release-[x.y.z] branch from tip of master (or whatever release commit)

bash git checkout master && git pull && git checkout -b release-2.1.0

  1. bump package.json + update CHANGELOG version links for all releasing packages (i.e., root + any resolvers)

In changelog for core plugin, normally leave Unreleased but update its link at the bottom to be rooted at the new version's tag, and add a link for the new version rooted at last version's tag.

```markdown

```

becomes

```markdown

```

Generally, don't use npm version for this because it creates a tag, which I normally wait until signoff from contributors and actually npm publish-ing to snap the tag.

  1. create pull request from release-[x.y.z] into release branch

I like this because it - lists all commits in the release - provides a commentary location to discuss the release - builds in CI and provides test results

  1. iterate on feedback
  2. handle other issues
  3. merge more PRs

  4. fix issues in changelog/docs

  5. npm publish from release-[x.y.z] branch

  6. don't forget resolvers!

  7. tag commit (v[x.y.z])

  8. again, not forgetting resolvers, if needed (resolvers/[name]/v[t.u.v])

  9. merge release-[x.y.z] into release (

  10. ideally fast-forward, probably with Git CLI instead of Github

  11. merge release into master

Done!