Upgrade release-please action workflow from v3 to v4 #2331
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
There was a problem hiding this comment.
Pull request overview
This PR upgrades the Release Please GitHub Action from v3 to v4, adopting the new manifest-first configuration model while maintaining backward compatibility with existing release history.
- Migrated from
GoogleCloudPlatform/release-please-action@v3togoogleapis/release-please-action@v4 - Added explicit GitHub Actions permissions for v4 compatibility
- Updated monorepo configuration to use v4-compatible syntax
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| release-please-config.json | Added v4 schema reference and migrated monorepo tagging configuration |
| .github/workflows/release-please.yml | Upgraded action version, added permissions block, and replaced deprecated v3 syntax with v4 equivalents |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
j-mes
commented
Jan 9, 2026
release-please-config.json
Outdated
Comment on lines
2
to
3
| "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json", | ||
| "include-component-in-tag": true, |
Member
Author
There was a problem hiding this comment.
We do need both of those lines in v4. I'm going to look at the config scripts to see why this is being removed by npm run regenerate and why it fails tests etc.
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.
Describe your changes
This PR upgrades Release Please from v3 to v4 and aligns our configuration with the v4 manifest-first model.
release-please-action@v3to@v4.command: manifestfrom the workflow (manifest mode is the default in v4).contents,pull-requests,issues).monorepo-tags: truetoinclude-component-in-tag.$schemaandinclude-component-in-tagtorelease-please-config.jsonfor v4 compatibility and validation.Behavioural impact
Notes
bootstrap-shaandlast-release-shaare intentionally retained to avoid altering historical release behaviour.ORIGAMI_GITHUB_TOKEN) is preserved to ensure CI workflows continue to run on Release Please PRs.GoogleCloudPlatformtoGoogleAPIson GitHub Actions. Something to keep an eye on.Migration guide / references
Additional context