Release Process
-
Update the worker version if necessary, based on semver rules. Run the following command:
npm run updateVersion -- --version <insert version>. Create a PR with those changes and merge before proceeding. -
Run the release pipeline with "IsPrerelease" unchecked and the "UploadPackageToPreReleaseFeed" variable set to "True"
-
Submit a PR to the host repo updating the NodeJsWorker package reference. Example PR here
-
Publish a GitHub release with the following note:
NOTE: This version of the worker was included with <insert version> of the host which has not finished rolling out in Azure yet.
-
Update the worker version using the command
npm run updateVersion -- --version <insert version>so that end-to-end tests continue to run against nightly prerelease builds. Otherwise the tests would be stuck using the package you just released. For example, if you just released "1.0.0", you should bump to "1.0.1" because "1.0.1-alpha.whatever" is greater than "1.0.0" which is greater than "1.0.0-alpha.whatever". We always bump the patch version in this step, even if the next release ends up being a minor or major release. -
Monitor the host rollout and update the GitHub release with the following note once it has finished:
NOTE: This version of the worker was included with <insert version> of the host which finished rolling out in <insert month and year>.