Skip to content

Release Process

Jump to bottom
Tsuyoshi Ushio edited this page May 13, 2026 · 7 revisions

  1. 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.

  2. Tag version against v3.x branch. e.g. v3.14.0.

    NOTE: If the mirror ci fails because of the tag already exists, go to the mirror repo and double check if the mirror repo's tag's commit matches with public repo ones.

  3. Run the build pipeline with choosing the tag and "IsPrerelease" unchecked to create a non-alpha nuget package artifact.

  4. Run the release pipeline, selecting the artifact from the build you just ran. This will upload the worker nuget package to a feed consumed by the host repo.

  5. Submit a PR to the host repo updating the NodeJsWorker package reference. Example PR here

  6. 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.

  7. 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.

  8. 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>.

Clone this wiki locally