[rush] Use Azure Pipelines app for version bump PRs - #6011
Merged
Bharat Middha (bmiddha) merged 8 commits intoSep 4, 2026
Merged
Conversation
Check out rushstack through the GitHubProjects service connection while preserving the source directory and triggering commit. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Declare the new repository resource to the 1ES pipeline template so YAML preview and source analysis accept the checkout. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Azure Pipelines already places the sole repository checkout at Build.SourcesDirectory, so no explicit path override is needed. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add none-type change files for downstream dependency range updates so automated bump PRs pass rush change --verify. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Run the same change-file validation as CI before publishing artifacts or pushing the automated branch. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Remove the exploratory change-file generation and verification steps so this PR remains scoped to GitHub App identity. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add none-type change files for downstream dependency range updates so automated bump PRs pass rush change --verify. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Run the same change-file validation as CI before publishing artifacts or pushing the automated branch. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
David Michon (dmichon-msft)
approved these changes
Sep 4, 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
2 participants
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.
Summary
Create the Rush and Rush Stack version-bump PRs using the
azure-pipelines[bot]GitHub App identity instead of the Rushbot user, and keep the generated bump branches compatible with the current published Rush release.Details
Both bump pipelines now check out
microsoft/rushstackthrough the existingGitHubProjectsGitHub service connection. The shared stage explicitly restores$(Build.SourceVersion)before creating the bump branch, so triggers and build-SHA tagging retain their existing semantics. The persisted checkout credential is then reused for the force-push and GitHub PR API calls.After committing the version bump, the pipeline temporarily runs
rush change --bulk --bump-type noneand commits the generated change files, then runsrush change --verifybefore packing or pushing. This handles dependency and peer-dependency range edits generated byrush version --bump, which the current published Rush exemption does not yet recognize and which caused the automated PR failures in #6009 and #6010.The underlying Rush fix is tracked by #6012. This compatibility step remains necessary until that fix is merged, published, and selected by this repository.
How it was tested
GitHubProjectsservice connection uses theInstallationTokenauthentication scheme.