npm version <step> normally creates a commit and a git tag for the version increment. However, since this is a monorepo, npm skips that step (presumably because it doesn't want to assume your release strategy).
release.sh could easily step in here by capturing the changes after npm version is run and creating a commit for it.
npm version <step>
normally creates a commit and a git tag for the version increment. However, since this is a monorepo,npm
skips that step (presumably because it doesn't want to assume your release strategy).release.sh
could easily step in here by capturing the changes afternpm version
is run and creating a commit for it.