ci: scope workflows to the v2.x maintenance branch - #256
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Scopes the v2 maintenance branch’s GitHub Actions automation so that CI and release-please operate independently from the new v3 (master) line, including preventing v2 patch releases from being marked as the repository’s “Latest” release.
Changes:
- Restrict
main.ymlandrelease.ymltriggers to pushes/PRs targetingv2.x(instead ofmaster). - Configure release-please to always bump patch versions on
v2.xviaversioning-strategy: always-bump-patch. - Add a post-release job to explicitly set
make_latest=falsefor releases cut fromv2.x.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
release-please-config.json |
Forces patch-only version bumps on the v2 maintenance line. |
.github/workflows/release.yml |
Runs release-please on v2.x and adds a job to unmark v2 releases as “Latest”. |
.github/workflows/main.yml |
Limits CI execution to pushes and PRs against v2.x. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Jun 11, 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
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
masteris now the v3 line;v2.x(cut from the last commit before #249) is the long-term maintenance branch for v2. This PR adapts the workflows onv2.xso v2 patches can be released independently — release-please operates per branch: the action'starget-branchdefaults to the branch that triggered the run, and the version is computed from this branch's.release-please-manifest.json(currently2.0.2).release.yml/main.yml: trigger on pushes / PRs tov2.xinstead ofmaster.release-please-config.json: setversioning-strategy: always-bump-patchso a strayfeat/feat!commit on the maintenance branch can never bump the version past 2.x.unmark-latestjob: GitHub marks the most recently created release as "Latest" by default, so a v2 patch released after v3.0.0 would steal the badge from the v3 line. The job flipsmake_latest=falseon every release cut from this branch (release-please has no built-in option for this — see Allow marking release aslatestwithmake_latestgoogleapis/release-please#2317).commitlint.ymlandupdate-metadata.ymlhave no branch filters and already work for PRs targetingv2.x; workflows onmasterare untouched.Testing
N/A (workflow-only change; will be exercised by the first v2 maintenance release)
Checklist
.changeset(N/A — this repo uses release-please)🤖 Generated with Claude Code