ci: add v1.x branch to main-checks workflow #1802
Merged
+1
−0
Conversation
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
Prepare for v2 development by ensuring CI runs on the v1.x maintenance branch. This branch will be created to receive security and critical bug fixes while main becomes the v2 development branch.
pcarleton
approved these changes
Dec 18, 2025
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.
Prepare for v2 development by ensuring CI runs on the v1.x maintenance branch.
Motivation and Context
As part of the v2 branching strategy, a
v1.xbranch will be created to receive security and critical bug fixes whilemainbecomes the v2 development branch. This PR ensures CI checks run on pushes to thev1.xbranch.The existing pattern
v*.*.*only matches branches with 3 segments (likev1.0.x), sov1.xneeds to be added explicitly.How Has This Been Tested?
Workflow syntax validated. The change will be tested when the
v1.xbranch is created and pushed to.Breaking Changes
None.
Types of changes
Checklist
Additional context
This is the first step in implementing the v2 branching strategy. After this is merged, the
v1.xbranch will be created frommainand branch protection will be configured.