Repository navigation
chore: move release-please to the release-please-oss action v6 - #712
Merged
Merged
Conversation
Move from googleapis/release-please-action to the release-please-oss fork, which sassysaint has used since 2025-08. Both wrap the same release-please library, so versioning, changelogs and commit parsing are unchanged. The workflow passes only token, config-file and manifest-file, which both actions accept, and reads releases_created, which both emit. Use the floating v6 major tag: the fork moves it on every release, and Dependabot will offer v7 when it ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Moves the release workflow from
googleapis/release-please-actionto therelease-please-oss/release-please-actionfork, at itsv6major tag. sassysaint has run on the fork since 2025-08.release-pleaselibrary, v17.6 vs v17.7, so version bumps, changelogs and commit parsing are unchanged.token,config-fileandmanifest-file, which both accept, and readsreleases_created, which both emit. The fork droppedversioning-strategyandrelease-as, which are not used here.v6tag. The fork moves it on every release; today it points at the same commit asv6.0.3.Verification
Workflow-only change, nothing to build or test locally. After merge, the next push to
mainshould run the release-please workflow green and leave the open release PR unchanged. A release PR that closes or is rebuilt from scratch would mean the action is reading the config differently.🤖 Generated with Claude Code