As a follow-up to the maintainers guide that was started in #5876 it would be good to include the rest of the release process that is a bit hard to infer
I think it looks like this:
npm run increment-version
npm run update-version # this runs in postversion but should probably be done before the npm install
npm install # make sure the package-lock.json is in the right state
npm run extract-codes # I don't see any other time this is called and it seems necessary for a release
npm run prepare-release # not strictly necessary but probably a good idea to make sure everything at least builds before tagging
git commit -a # I think that npm run postversion wouldn't work if there are any pending changes
npm run postversion
npm run release
npm run publish-extension
I included the extra steps between update-version and postversion because I think there might be a subtle bug or two in npm run postversion:
npm install && npm run update-version may leave package-lock.json in a state where it references some older versions.
It also seems like a the right time to run npm run extract-codes?
As a follow-up to the maintainers guide that was started in #5876 it would be good to include the rest of the release process that is a bit hard to infer
I think it looks like this:
npm run postversionwouldn't work if there are any pending changesI included the extra steps between update-version and postversion because I think there might be a subtle bug or two in
npm run postversion:npm install && npm run update-versionmay leave package-lock.json in a state where it references some older versions.npm run extract-codes?