Repository navigation
ci(release): use single-dash Release Please branch names - #410
Merged
Merged
Conversation
aghassemlouei
requested review from
Calvin-Cheng1,
LanceWray and
mgcarey-google
November 10, 2026 03:07
aghassemlouei
marked this pull request as ready for review
November 10, 2026 03:12
12 of 19 tasks
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.
Description
Replaces the double-dash
release-please--branches--mainnaming convention withrelease-please-branches-mainfor future Release Please pull requests while keeping in-flight v6.0.0 release pull request #394 on its existingrelease-please--branches--mainbranch until v6.0.0 merges:BranchName.ofTargetBranch,DefaultBranchName, andAutoreleaseBranchName.matchesinside.github/workflows/release.ymlto emitrelease-please-branches-<target>while still parsing legacyrelease-please--branches--<target>branch names when cutting Git tags and GitHub Releases on merge.Manifest.createOrUpdatePullRequestand the changelog sub-bullet pre-step in.github/workflows/release.ymlto update any openrelease-please--branches--mainpull request in place and read curated* ...sub-bullets from both legacy and single-dash release branches, switching torelease-please-branches-mainonce #394 merges.GEMINI.mdand expandstests/test_label_taxonomy.pyto cover single-dash branch generation, legacy branch parsing,AutoreleaseBranchNameprefix exclusion, and in-place updates for open legacy release pull requests.No GitHub issue exists for this change.
Type of Change
Deployment & Compliance Impact
Checklist
Code Quality & Reusability
modules/orfast/stages-aw/can be leveraged for this change.docs/naming-convention.md.Documentation
README.mdof the modified module or blueprint.Security
Testing
Testing Performed
.github/workflows/release.ymlruntimesedand Node.js patch directly against the bundledgoogleapis/release-please-actionv5.0.0dist/index.js(node --checkplus runtime verification ofBranchName.ofTargetBranch('main'),BranchName.parseacross single-dash and legacy double-dash branches, andAutoreleaseBranchName.matchesonrelease-please-branches-v6.0).bash tools/run_tests.sh(122Python unit tests including expandedtest_release_workflow_normalizes_issue_and_pr_links_to_numberscoverage,32shell syntax checks,test_common_functions.sh,test_sync_from_cff.sh,test_tflint.sh, boilerplate header verification, and AST unused-variable checks).bash tools/lint.sh(all10repository lint gates passed, includingruff format --checkandruff checkacross383Python files).