Skip to content

Don't require approval on publish phase of namereserve pipeline#46798

Merged
scbedd merged 1 commit intoAzure:mainfrom
scbedd:namereserve-approval-change
May 8, 2026
Merged

Don't require approval on publish phase of namereserve pipeline#46798
scbedd merged 1 commit intoAzure:mainfrom
scbedd:namereserve-approval-change

Conversation

@scbedd
Copy link
Copy Markdown
Member

@scbedd scbedd commented May 8, 2026

If we've gotten there, we intend it.

@scbedd scbedd self-assigned this May 8, 2026
Copilot AI review requested due to automatic review settings May 8, 2026 19:29
@scbedd scbedd requested review from benbp and weshaggard as code owners May 8, 2026 19:29
@scbedd scbedd moved this from 🤔 Triage to 🔬 Dev in PR in Azure SDK EngSys 🚀🌒🧑‍🚀 May 8, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the name-reserve publish pipeline stage to avoid using the package-publish deployment environment, removing the associated manual approval gate for the PyPI publish deployment.

Changes:

  • Switch the PublishPackage deployment job environment from package-publish to none to prevent requiring environment-based approvals during the publish stage.
Show a summary per file
File Description
eng/pipelines/templates/stages/publish-namereserve-package.yml Changes the deployment job’s environment to avoid approval gating on the publish stage.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@scbedd scbedd merged commit 443bdb0 into Azure:main May 8, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants