workflow: add release-vfsforgit to automate VFS for Git updates#871
Open
mjcheetham wants to merge 1 commit intomicrosoft:vfs-2.53.0from
Open
workflow: add release-vfsforgit to automate VFS for Git updates#871mjcheetham wants to merge 1 commit intomicrosoft:vfs-2.53.0from
mjcheetham wants to merge 1 commit intomicrosoft:vfs-2.53.0from
Conversation
When a new microsoft/git release is published, VFS for Git needs to pick up the new Git version. Today this is a manual process. This workflow automates it by reacting to GitHub release events: - Full releases: creates a PR in microsoft/VFSForGit to bump the default GIT_VERSION in the build workflow, so future CI runs and manual dispatches use the latest stable Git version. - Pre-releases: triggers a VFS for Git build via workflow_dispatch with the pre-release tag, allowing early validation of release candidates without changing the checked-in default. Authentication uses the existing Azure Key Vault + OIDC pattern (matching release-homebrew and release-winget) to retrieve a token with write access to the VFS for Git repository. Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
derrickstolee
approved these changes
Mar 27, 2026
derrickstolee
left a comment
There was a problem hiding this comment.
Nice. A good reminder and version pin updates should be easy like this.
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.
When a new microsoft/git release is published, VFS for Git needs to pick up the new Git version. Today this is a manual process. This workflow automates it by reacting to GitHub release events:
Full releases: creates a PR in microsoft/VFSForGit to bump the default
GIT_VERSIONin the build workflow, so future CI runs and manual dispatches use the latest stable Git version.Pre-releases: triggers a VFS for Git build via
workflow_dispatchwith the pre-release tag, allowing early validation of release candidates without changing the checked-in default.Authentication uses the existing Azure Key Vault + OIDC pattern (matching
release-homebrewandrelease-winget) to retrieve a token with write access to the VFS for Git repository.Corresponding PR in
microsoft/VFSForGit: microsoft/VFSForGit#1926