Release Process

1. Verify the end-to-end tests have passed after all changes have been merged. These are run nightly, so manually queue a test run if you merged a change the same day you plan to release.

2. Update the package version based on semver rules. Run the following command: npm run updateVersion -- --version <insert version>.

3. Run the build pipeline with "IsPrerelease" unchecked. Wait for the build to finish before moving to the next step.

4. Ensure Access Requirements

   • Follow the partner release wiki:
     https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1/Partner-Release-Pipeline
   • Verify access to the required security group:
     https://coreidentity.microsoft.com/manage/Entitlement/entitlement/azuresdkpart-heqj

5. Upload TGZ to Partner Release Blob

   • Locate the generated .tgz package file.
   • Upload it to the correct team location in the blob container:
     https://ms.portal.azure.com/#view/Microsoft_Azure_Storage/ContainerMenuBlade/~/overview/storageAccountId/%2Fsubscriptions%2Fa18897a6-7e44-457d-9260-f2854c0aca42%2FresourceGroups%2Fazuresdkpartnerdrops%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fazuresdkpartnerdrops/path/drops/etag/%220x8D680AE5A72EEFF%22

6. Run JS Partner Release Pipeline

   • Open the JS partner-release pipeline:
     https://dev.azure.com/azure-sdk/internal/_build?definitionId=6992&_a=summary
   • Run the pipeline using this path convention:

     <team>/<language>/<version>
     

   • Example:

     azure-functions/azure-functions-nodejs-extensions-servicebus/0.2.0-preview
     

7. Install the package you just released and sanity test that it worked.

8. Publish a GitHub release.