fix: split publish pipeline into separate stage with release job isolation#2894
Merged
Conversation
…ation Replace isReleaseJob on the build job with a separate publish stage containing two jobs: publish_internal (no release context) and publish_public (releaseJob + isProduction). This prevents the 1ES template from flagging release tasks outside of release jobs. Also uses artifactName (required by 1ES template) for pipelineArtifact inputs, and passes version variables across stages via output variables. Co-authored-by: Copilot <[email protected]>
Contributor
There was a problem hiding this comment.
Pull request overview
Splits the manual npm publish Azure DevOps pipeline into a dedicated publish stage with isolated jobs for internal feed publishing vs ESRP public publishing, aligning with 1ES change-management requirements (release tasks only in release jobs).
Changes:
- Adds a
publishstage withpublish_internal(Azure Artifacts) andpublish_public(type: releaseJob,isProduction: true, ESRP) jobs. - Publishes
out/as apipelineArtifact(artifactName: npm-packages) and consumes it from$(Pipeline.Workspace)in publish jobs. - Promotes
VersionNumber/NpmTagto cross-stage output variables for release metadata.
heyitsaamir
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Same fix as microsoft/teams.ts#625 and microsoft/teams.py#481.
Splits the single-job publish pipeline into a separate
publishstage with two jobs:publish_internal- no release context, publishes to Azure Artifactspublish_public-type: releaseJob+isProduction: true, publishes via ESRPThis fixes the 1ES template error:
Also uses
artifactName(required by 1ES template) forpipelineArtifactinputs.