ci: make scheduled branch matrix dynamic - #5412
Open
kolyshkin wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Alas no way to test this until we merge. |
The list of branches to run periodical CI on was hardcoded, meaning it had to be manually updated on every minor release (add the new release branch, drop the one that falls out of support per RELEASES.md), and would silently keep testing unsupported branches if we forgot. Instead, list the repo branches via the API and pick the three most recent release-X.Y ones (latest, latest-1, latest-2), plus main. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kolyshkin
force-pushed
the
scheduled-dynamic-matrix
branch
from
August 24, 2026 19:57
0f3f9fa to
e869baa
Compare
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
1 participant
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.
Follow-up to #5393 (review comment).
The list of branches to run periodical CI on was hardcoded, meaning it had to be manually updated on every minor release (add the new release branch, drop the one that falls out of support per RELEASES.md), and would silently keep testing unsupported branches if we forgot.
Instead, a
preparejob lists the repo branches via the API and picks the three most recentrelease-X.Yones (latest,latest-1,latest-2), plusmain, feeding them into the matrix viafromJSON.Running the same selection logic against the current branch list of this repo yields
["main", "release-1.5", "release-1.4", "release-1.3"], i.e. exactly the list that was hardcoded before, so there is no behavior change today.🤖 Generated with Claude Code