chore(deps): update googleapis/release-please-action action to v5#1019
chore(deps): update googleapis/release-please-action action to v5#1019renovate[bot] wants to merge 1 commit into
Conversation
Deploying control-layer with
|
| Latest commit: |
432587e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bd3c9a22.control-layer.pages.dev |
| Branch Preview URL: | https://renovate-googleapis-release.control-layer.pages.dev |
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
10 times, most recently
from
880f123 to
9bb3352
Compare
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
5 times, most recently
from
6c4e8b1 to
cb85de4
Compare
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
5 times, most recently
from
a39df0a to
3fa8c52
Compare
![doubleword-code[bot]](https://avatars.githubusercontent.com/in/3610877?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. This is a routine dependency upgrade with no functional changes required to the workflow configuration.
Verdict: Ready to approve - the change is minimal, safe, and follows best practices.
Research notes
Fetched the release-please-action v5.0.0 release page:
- Breaking change in v5: Upgrade to Node.js 24 runtime only - no API or configuration changes
- Bug fixes: Includes release-please core bump from 17.3.0 to 17.6.0
- Configuration compatibility: The existing workflow using
config-fileandmanifest-fileparameters remains fully compatible - Permissions: Current workflow has all required permissions (
contents: write,pull-requests: write,issues: write)
The repository's release-please-config.json correctly specifies release-type: rust at the package level, which is the recommended approach for manifest-based configuration.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date
- Monitor the next release cycle to confirm the action runs successfully (standard practice for any CI/CD change)
General findings
None. This is a clean, low-risk dependency update.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
3fa8c52 to
e3f1da6
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5 in the release workflow file. This is a straightforward dependency bump that brings the action to the latest major version.
Verdict: Approve - The change is minimal, safe, and follows best practices for GitHub Actions versioning.
Research notes
I reviewed the release-please-action v5.0.0 changelog:
- v5.0.0 (2026-04-22): Breaking change - upgraded to Node.js 24 runtime. Also includes bug fix bumps for release-please from 17.3.0 to 17.6.0.
- v4.x series: Previously used Node.js 20 runtime (v4.0.0 upgraded from node16 to node20).
The migration from v4 to v5 is transparent for users because:
- The action's public API inputs (
config-file,manifest-file,token) remain unchanged - The workflow configuration requires no modifications
- Node.js 24 is available on GitHub Actions
ubuntu-latestrunners
The repository already uses the manifest-based configuration approach (release-please-config.json + .release-please-manifest.json), which was introduced in v4.0.0 and continues to be the default in v5.
Suggested next steps
- Merge this PR to update the action version
- Monitor the next release-please workflow run to confirm successful execution (standard practice for any CI/CD change)
General findings
No issues identified. The single-line change correctly updates the action reference from @v4 to @v5. The existing workflow configuration is compatible with v5's input schema.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
e3f1da6 to
834aef7
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. The change is a single-line version bump in .github/workflows/release-please.yaml. Verdict: Ready to approve - the update is straightforward and compatible with the existing configuration.
Research notes
Fetched the release-please-action repository and CHANGELOG.md:
- v5.0.0 (April 22, 2026) has one breaking change: upgrade to Node.js 24 runtime
- Also includes bug fix: bump release-please from 17.3.0 to 17.6.0
- The workflow uses manifest-based configuration (
config-file+manifest-file), which is the recommended approach and remains fully compatible with v5 - No input parameter changes are required for this migration
Suggested next steps
- Verify GitHub runner compatibility: Ensure the organization's GitHub Actions runners support Node.js 24 (ubuntu-latest should support it as of 2026)
- Monitor first run: After merging, watch the first release-please workflow run to confirm no regressions
General findings
None. This is a routine dependency update with no identified issues. The existing manifest-based configuration (release-please-config.json with rust release type and cargo-workspace plugin) does not require any changes.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
834aef7 to
c5870ee
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5 in the release workflow. Based on my research of the release-please-action v5.0.0 release notes, this is a straightforward dependency upgrade with one breaking change: the action now runs on Node.js 24 (upgraded from Node.js 20 in v4).
The change is minimal and low-risk:
- Only modifies the action version reference in
.github/workflows/release-please.yaml - No configuration changes required—the existing manifest-based config (
release-please-config.jsonand.release-please-manifest.json) remains compatible - The underlying
release-pleaselibrary was also bumped from 17.3.0 to 17.6.0, bringing bug fixes
Verdict: Ready to approve. This is a routine maintenance update that keeps the release automation on a supported Node.js runtime.
Research notes
Fetched the release-please-action v5.0.0 release page:
- Breaking change: "upgrade to node24" — GitHub Actions will run this action on the Node.js 24 runtime. This is transparent to users unless the action relies on deprecated Node.js APIs (unlikely for a well-maintained Google action).
- Bug fix: "bump release-please from 17.3.0 to 17.6.0" — brings patch-level improvements to the release-please library itself.
The current workflow configuration uses the manifest-based approach (config-file and manifest-file parameters), which is the recommended pattern and remains unchanged between v4 and v5 per the README documentation.
Suggested next steps
- Merge this PR — no code changes required.
- Monitor the next release cycle — after merging, observe the next release PR creation to confirm the action runs successfully on Node.js 24. If any issues arise, they would likely surface as workflow run failures visible in the Actions tab.
General findings
None. The change is isolated to a single line in the workflow file, and the upgrade path is well-documented by the upstream maintainers.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
c5870ee to
9aedd5e
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. The update is straightforward and maintains compatibility with the existing workflow configuration.
Verdict: Ready to approve — no changes required.
Research notes
Fetched the release-please-action v5.0.0 release notes:
- Breaking change: Upgrade to Node.js 24 runtime (affects action internals, not user-facing API)
- Bug fixes: release-please core bumped from 17.3.0 to 17.6.0
The v4→v5 migration guide indicates breaking changes only relate to:
- Removal of the
commandinput option (deprecated in favor ofskip-github-release/skip-github-pull-request) - Package options moved to manifest config
This repository already uses manifest-based configuration (config-file: release-please-config.json, manifest-file: .release-please-manifest.json), so neither breaking change affects this workflow.
Suggested next steps
- Merge this PR as-is — the update is safe and brings bug fixes from the upstream release-please project.
- Consider monitoring the first release cycle after merge to confirm the action behaves as expected (standard practice for any CI/CD change).
General findings
None. This is a clean, low-risk dependency update with no identified issues.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
9aedd5e to
c38ba27
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. The change is a single-line version bump in the release workflow configuration.
According to the v5.0.0 release notes, the only breaking change is an internal upgrade to Node 24, which is transparent to workflow users. The action also includes bug fixes from release-please 17.3.0 → 17.6.0. The manifest-based configuration currently in use (config-file and manifest-file parameters) remains fully compatible.
Verdict: Ready to approve – this is a safe, routine dependency update with no required configuration changes.
Research notes
- Fetched googleapis/release-please-action repository page – confirmed v5.0.0 was released Apr 22, 2026
- Fetched v5.0.0 release notes – identified Node 24 upgrade as the only breaking change (internal to action runtime)
- Reviewed current workflow config – uses manifest-based approach which is unchanged in v5
Suggested next steps
- Merge this PR – no changes required
- Optionally verify the first automated release PR created by v5 works as expected (standard due diligence for any release automation change)
General findings
None – the change is minimal and well-scoped.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
2 times, most recently
from
c38ba27 to
d3cb95a
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. This is a routine dependency update with one breaking change (internal Node 24 runtime upgrade) that does not affect the workflow configuration.
Verdict: Ready to approve — the change is minimal, well-scoped, and compatible with the existing workflow configuration.
Research notes
Fetched the v5.0.0 release notes:
- Breaking change: Upgrade to Node 24 runtime (internal to the action, no user-facing impact)
- Bug fix: Bumps underlying release-please from 17.3.0 to 17.6.0
The existing workflow uses the manifest-based configuration pattern (config-file and manifest-file parameters), which is the recommended approach that remains unchanged between versions.
Suggested next steps
- Merge this PR to keep the release automation up to date
- Monitor the next release-please run to confirm normal operation (expected to work without issues)
General findings
No issues identified. The workflow configuration is already aligned with v5 requirements:
- Uses manifest-based configuration (correct for both v4 and v5)
- Has appropriate permissions (
contents: write,pull-requests: write,issues: write) - Uses a custom
RELEASE_TOKENsecret rather thanGITHUB_TOKEN, which avoids the recursive workflow trigger limitation
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
d3cb95a to
d19a120
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. The change is a straightforward one-line version bump in the workflow file. According to the v5.0.0 release notes, the only breaking change is an upgrade to Node 24 runtime, which is transparent to users. The existing manifest-based configuration is fully compatible with v5.
Verdict: Ready to approve - no changes needed.
Research notes
- Fetched release-please-action GitHub page - confirmed v5.0.0 was released on Apr 22, 2026
- Fetched v5.0.0 release notes - breaking change is "upgrade to node24", which requires no workflow file changes
- Reviewed current workflow configuration at
.github/workflows/release-please.yaml- uses manifest-based approach withconfig-fileandmanifest-fileparameters, which is the recommended pattern - Verified
release-please-config.jsonand.release-please-manifest.jsonare present and properly configured for the Rust workspace
Suggested next steps
- Merge this PR as-is - no modifications required
- Monitor the first release cycle after merge to confirm the action runs successfully (standard practice for any CI/CD change)
General findings
None - this is a clean, low-risk dependency update with no identified issues.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
d19a120 to
432587e
Compare
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5 in the release workflow. According to the upstream changelog, v5.0.0 contains one breaking change (upgrade to Node 24 runtime) and bug fixes including bumping release-please from 17.3.0 to 17.6.0.
Verdict: Ready to approve - low-risk dependency update with no configuration changes required.
Research notes
- Fetched release-please-action GitHub page - confirmed v5.0.0 released Apr 22, 2026
- Fetched CHANGELOG.md - v5.0.0 breaking change is Node 24 runtime upgrade (transparent to users)
- Current workflow uses manifest-based config (
config-file,manifest-file) which remains fully supported in v5 - No input parameter changes affect this workflow's configuration
Suggested next steps
- Approve and merge - This is a routine dependency update with no identified risks
- Monitor first run - After merge, verify the release-please workflow runs successfully on the next push to main
General findings
None - this is a straightforward version bump with no code changes beyond the action reference.
This PR contains the following updates:
v4→v5Release Notes
googleapis/release-please-action (googleapis/release-please-action)
v5.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
v5.0Compare Source
v5Compare Source
v4.4.1Compare Source
v4.4.0Compare Source
Features
Bug Fixes
changelog-hostparameter ignored when using manifest configuration (#1151) (535c413)v4.4Compare Source
v4.3.0Compare Source
Features
v4.3Compare Source
v4.2.0Compare Source
Features
v4.2Compare Source
v4.1.5Compare Source
Bug Fixes
v4.1.4Compare Source
Bug Fixes
v4.1.3Compare Source
Bug Fixes
v4.1.2Compare Source
Bug Fixes
v4.1.1Compare Source
Bug Fixes
v4.1.0Compare Source
Features
changelog-hostinput toaction.yml(#948) (863b06f)v4.1Compare Source
v4.0.3Compare Source
Bug Fixes
v4.0.2Compare Source
Bug Fixes
v4.0.1Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.