- https://gerrit.wikimedia.org/r/824162 repeats what was already done in https://gerrit.wikimedia.org/r/763245, but in the wrong codebase.
- https://gerrit.wikimedia.org/r/824410
- https://gerrit.wikimedia.org/r/824698
- Actually tag the release. It appears this is done exclusively on npm, not via a git tag, branch or anything.
- https://gerrit.wikimedia.org/r/825718 use it in Kartotherian
- https://gerrit.wikimedia.org/r/c/826224 use it in Kartographer
For future reference:
- Update the version number in package.json. Check if package-lock.json needs an update as well (run npm install). Make sure all this is merged to master.
- git tag v0.7.0. This is sometimes done without the v, but it seems it's convention to have it.
- git push --tags
- npm adduser if this was not done before.
- npm publish
Source: https://cloudfour.com/thinks/how-to-publish-an-updated-version-of-an-npm-package/