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: |
b3ccb2a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4eef509b.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.
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 routine dependency update with no configuration changes required.
Verdict: Safe to merge – no breaking changes for the current manifest-based configuration.
Research Notes
Per the v5.0.0 release notes:
- Main change: Upgrade to Node 24 runtime (internal to action execution)
- Bug fixes: Bumps release-please from 17.3.0 to 17.6.0
- No breaking changes to manifest-mode configuration (
config-file,manifest-file)
The repository uses manifest-based configuration via release-please-config.json and .release-please-manifest.json, which remains fully compatible with v5.
Suggested Next Steps
- Merge this PR – it's a safe, low-risk dependency update.
- Monitor the next automated Release PR creation to confirm normal operation (standard practice for release tooling updates).
General Findings
No issues identified. The workflow already has the required permissions (contents: write, issues: write, pull-requests: write), and the rust release-type configured in release-please-config.json is supported in both v4 and v5.
renovate
Bot
force-pushed
the
renovate/googleapis-release-please-action-5.x
branch
from
cf77202 to
358eaaf
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. This is a routine dependency upgrade with no code changes required beyond the version bump.
Verdict: Ready to approve - The change is minimal and safe.
Research notes
I reviewed the v5.0.0 release notes for release-please-action:
- Breaking change: Upgrades to Node.js 24 runtime (from Node.js 20 in v4)
- Bug fixes: Bumps release-please from 17.3.0 to 17.6.0
- The action maintains backward compatibility for all configuration options used in this repository (
config-file,manifest-file,token)
The workflow file at .github/workflows/release-please.yaml uses the manifest-based configuration approach with config-file and manifest-file parameters, which continues to be fully supported in v5.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date
- Monitor the next release cycle to ensure the workflow runs correctly with v5 (standard practice for any CI/CD update)
General findings
No issues identified. The change is:
- Safe: Only a version tag update; all used configuration options remain compatible
- Beneficial: Brings bug fixes from release-please 17.3.0 → 17.6.0 and Node.js 24 runtime improvements
- Low risk: GitHub Actions failures would be immediately visible in the Actions tab, and the workflow can be quickly reverted if needed
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. This is a routine dependency upgrade with minimal risk.
Verdict: Ready to approve - no blocking issues identified.
Research notes
Based on the v5.0.0 release notes:
- Breaking change: Upgraded to Node.js 24 runtime (affects action internals, not user-facing configuration)
- Bug fixes: Bumped release-please from 17.3.0 to 17.6.0
- The action maintains backward compatibility for all configuration options used in this workflow (
config-file,manifest-file,token)
The current workflow configuration uses the manifest-based approach (.release-please-config.json and .release-please-manifest.json), which is fully supported in v5.
Suggested next steps
- Merge this PR after confirming the
RELEASE_TOKENsecret is properly configured (already required for v4) - Monitor the first release workflow run after merge to confirm successful execution
General findings
No issues found. The change is minimal (single line) and follows Renovate's standard update pattern. The v5 release notes indicate no breaking changes that would affect the current workflow configuration.
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. After reviewing the change and researching the upstream release notes, this is a safe dependency upgrade that only changes the underlying Node.js runtime version (Node 20 → Node 24). No configuration changes or breaking changes affect this repository's usage pattern.
Verdict: Ready to approve — no blockers identified.
Research notes
I fetched the release-please-action repository page and CHANGELOG.md to understand what changed between v4 and v5:
- v5.0.0 (2026-04-22):
⚠️ Breaking change: Upgraded to Node 24 runtime- Bug fix: Bumped release-please from 17.3.0 to 17.6.0
- v4.x series ran on Node 20 (since v4.0.0)
The workflow uses the manifest-based configuration (config-file and manifest-file options), which remains unchanged between versions. The breaking change (Node 24) is transparent to users since GitHub Actions runners handle the runtime.
Suggested next steps
- Merge this PR as-is — the change is safe and follows standard dependency update practices
- Consider enabling Dependabot/Renovate auto-merge for similar minor/major action updates in the future to reduce review overhead
General findings
No issues found. The change is minimal, well-scoped, and the upstream documentation confirms backward compatibility for the configuration options used in this repository.
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. The change is a single-line version bump in .github/workflows/release-please.yaml.
Verdict: Approved — This is a routine dependency update with minimal risk.
Research notes
I fetched the release-please-action v5.0.0 release notes. The breaking changes are:
- Upgrade to Node 24 — The action now runs on Node.js 24 runtime. This is transparent to users since GitHub-hosted runners (ubuntu-latest) support Node 24.
- release-please core upgraded from 17.3.0 to 17.6.0 — Internal bug fixes, no user-facing impact expected.
The existing workflow configuration (config-file, manifest-file, token) remains compatible with v5 — no migration required for this project's usage pattern.
Suggested next steps
- Merge this PR — No additional changes required.
- Monitor the next release-please run — After merge, verify the next push to
maintriggers the workflow successfully (standard practice for any CI/CD change).
General findings
No issues identified. The PR is correctly scoped as a chore(deps) update, and the version change aligns with the upstream v5.0.0 release from April 2026.
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. This is a routine dependency upgrade that brings the project to the latest major version of the release automation tool.
Verdict: Ready to approve - this is a safe, well-scoped dependency update with no breaking changes for the current configuration.
Research notes
Fetched the official GitHub repository page and v5.0.0 release notes:
- v5.0.0 release date: April 22, 2026
- Breaking change: Upgrade to Node.js 24 runtime (internal to the action, does not affect workflow configuration)
- Bug fixes: Includes release-please core bump from 17.3.0 to 17.6.0
- Compatibility: The manifest-based configuration used by this project (
config-file: release-please-config.json,manifest-file: .release-please-manifest.json) remains fully compatible between v4 and v5
The v4→v5 migration primarily involves internal runtime updates. No workflow YAML changes are required beyond the version tag update shown in this PR.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date
- Monitor the next release PR created by release-please to confirm the upgrade works as expected (standard practice for any CI/CD tooling update)
General findings
No issues identified. The change is minimal (single line), follows Renovate's automated update pattern, and aligns with the project's existing manifest-based release-please configuration.
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 upgrade that keeps the repository's CI/CD tooling current.
Verdict: Ready to approve - this is a routine maintenance update with no identified risks.
Research notes
I reviewed the release-please-action changelog for v5.0.0 (released April 22, 2026). The key changes are:
-
Breaking change: Upgrade to Node 24 runtime - This is transparent to users since the action runs in GitHub's managed Ubuntu runner environment.
-
Bug fix: Bumps release-please from 17.3.0 to 17.6.0 - These are internal dependency updates that bring bug fixes and improvements to the underlying release-please tool.
The current workflow configuration uses manifest-based releases (config-file: release-please-config.json, manifest-file: .release-please-manifest.json), which has been the recommended approach since v4.0.0 and remains unchanged in v5. No migration steps are required for this configuration.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date.
- Consider enabling Dependabot or Renovate for automatic GitHub Actions updates if not already configured (this PR appears to be from Renovate).
General findings
No issues identified. The change is minimal (single line), low-risk, and follows semantic versioning best practices by pinning to major versions. The existing workflow permissions (contents: write, pull-requests: write, issues: write) are appropriate for release-please and do not need adjustment for v5.
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 routine dependency upgrade that brings the repository to the latest major version of the release automation tool.
Verdict: Ready to approve - this is a safe, well-scoped change with no breaking implications for the current configuration.
Research notes
Fetched the release-please-action repository page and CHANGELOG.md:
- v5.0.0 (2026-04-22): Breaking change - upgraded to Node 24 runtime. Also includes bug fix bumping release-please from 17.3.0 to 17.6.0.
- v4.4.1 (2026-02-20): Bug fixes releasing release-please from 17.1.3 to 17.3.0.
- The project uses manifest-based configuration (
release-please-config.jsonand.release-please-manifest.json), which was introduced as the default in v4.0.0.
The v5 breaking change (Node 24 runtime) is transparent to users - it only affects the action's internal execution environment, not the interface or behavior.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date.
- Consider enabling Dependabot/Renovate for GitHub Actions to catch these updates automatically (if not already configured).
General findings
No issues found. The change is minimal and low-risk:
- Only one line changed in the workflow file
- The existing manifest-based configuration (
config-file,manifest-file) remains compatible with v5 - The token-based authentication pattern is unchanged
- No custom inputs are used that might have been affected by breaking changes between v4 and v5
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. This is a routine dependency upgrade that brings in the latest release-please features and bug fixes.
Verdict: Ready to approve, with one consideration noted below.
Research notes
Fetched the release-please-action repository and CHANGELOG:
- v5.0.0 (April 22, 2026) is a major version release
- Breaking change: Upgrades runtime to Node.js 24 (from Node.js 20 in v4)
- Includes release-please core library bump from 17.3.0 to 17.6.0 with bug fixes
- The workflow uses
ubuntu-latestwhich supports Node 24, but teams with self-hosted runners should verify runner compatibility
Suggested next steps
- Merge this PR if using GitHub-hosted runners (default)
- If using self-hosted runners, verify they have Node.js 24 installed before merging
General findings
No issues found. The change is minimal and follows standard dependency update practices. The workflow configuration remains unchanged since it uses the manifest-based configuration pattern (config-file and manifest-file inputs) which is consistent across v4 and v5.
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action GitHub Action from v4 to v5. According to the v5.0.0 release notes, the main change is an upgrade to Node.js 24 runtime, along with bumping release-please from 17.3.0 to 17.6.0. The workflow configuration uses standard manifest-based options that remain compatible.
Verdict: Ready to approve - this is a low-risk dependency update with no breaking changes to the action's input/output interface.
Research Notes
- Fetched release-please-action v5.0.0 release notes
- Breaking change in v5: Node.js 24 runtime upgrade (internal to the action)
- Bug fixes include release-please core bump from 17.3.0 → 17.6.0
- All workflow options used (
config-file,manifest-file,token) remain supported - Workflow permissions (
contents: write,pull-requests: write,issues: write) match required permissions per official docs
Suggested Next Steps
- Merge this PR to keep the release automation tooling current
- Monitor the next release PR creation to verify the action works as expected
- Consider pinning to a specific minor version (e.g.,
@v5.0.0) instead of@v5if you want stricter version control over future updates
General Findings
No blocking issues identified. The change is minimal, well-scoped, and follows the project's existing release-please manifest configuration pattern.
There was a problem hiding this comment.
Summary
This PR updates the googleapis/release-please-action from v4 to v5 in the release workflow. This is a minor dependency maintenance change with a single-line modification.
Verdict: Ready to approve - low-risk update with no breaking changes for the current configuration.
Research notes
Fetched the release-please-action repository and CHANGELOG.md:
- v5.0.0 (April 22, 2026): Breaking change - upgrade to Node.js 24 runtime
- Also includes: bump release-please from 17.3.0 to 17.6.0
- The current manifest-based configuration (
config-file,manifest-file) remains fully compatible
The v4→v5 transition does not require any config changes for repositories already using manifest-based configuration like this one.
Suggested next steps
- Merge this PR as-is - the change is safe and follows standard dependency update practices
- Consider enabling Renovate's auto-merge for similar minor/major action updates if not already configured
General findings
No issues found. The update is:
- Correctly scoped (only changes the action version reference)
- Following semantic versioning conventions (major bump = breaking changes, but none affect this usage pattern)
- Consistent with the project's use of Renovate for dependency management
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.
Verdict: Ready to approve - This is a routine dependency update with no compatibility concerns for this repository's configuration.
Research notes
Fetched the v5.0.0 release notes:
- Breaking change: Upgraded to Node 24 runtime (internal to the action, doesn't affect workflow configuration)
- Bug fixes: Bumped underlying release-please from 17.3.0 to 17.6.0
Reviewed the action's README - the workflow's manifest-based configuration (config-file and manifest-file parameters) is the recommended approach for v5 and remains unchanged from v4.
Analysis
The workflow configuration is fully compatible with v5:
- Uses manifest-based config (
.release-please-manifest.json+release-please-config.json), which is the advanced configuration pattern supported by both versions - Declared permissions (
contents: write,pull-requests: write,issues: write) match the action's requirements per documentation - Workflow trigger (push to main) is the standard pattern
- No deprecated inputs are being used
The Node 24 runtime upgrade is transparent to workflow consumers - GitHub Actions handles the runtime automatically.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date
- Consider enabling Dependabot or Renovate auto-merge for minor/patch GitHub Actions updates to reduce PR overhead
There was a problem hiding this comment.
Summary
This PR updates the release-please-action GitHub Action from v4 to v5. The change is minimal (single line in the workflow file) and low-risk. According to the v5.0.0 release notes, the only breaking change is an internal upgrade to Node.js 24, which does not affect configuration or usage. The workflow already uses the recommended manifest-based configuration and has all required permissions.
Verdict: Ready to approve.
Research notes
- Fetched release-please-action GitHub page and v5.0.0 release notes
- v5.0.0 changelog shows:
- Breaking: Upgrade to node24 (internal runtime change, no config impact)
- Features: Same node24 upgrade
- Fixes: Bump release-please from 17.3.0 to 17.6.0
- Current workflow uses manifest config (
config-file,manifest-file) which is the recommended approach and unchanged in v5 - Workflow permissions (
contents: write,pull-requests: write,issues: write) match documented requirements - Token configuration uses custom
RELEASE_TOKENsecret, which is correct for enabling CI checks on Release Please PRs
Suggested next steps
- Merge this PR
- Monitor the next release PR creation to confirm the action runs successfully
General findings
None — this is a clean, routine dependency update.
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. This is a routine dependency upgrade with minimal changes (single line change).
Verdict: Ready to approve, but teams should be aware of the breaking change.
Research notes
I reviewed the v5.0.0 release notes for release-please-action:
- Breaking change: v5 upgrades to Node.js 24 runtime (from Node.js 16/18/20 in v4)
- Bug fix: Includes bump of release-please core from 17.3.0 to 17.6.0
- The action maintains backward compatibility for all configuration options used in this repository (
config-file,manifest-file,token)
The current workflow configuration at .github/workflows/release-please.yaml uses:
config-file: release-please-config.jsonmanifest-file: .release-please-manifest.jsontoken: ${{ secrets.RELEASE_TOKEN }}
All these inputs remain supported in v5 per the official documentation.
Suggested next steps
- Merge this PR - The update is safe and follows standard dependency maintenance practices
- Monitor the first release run - After merge, watch the next release-please workflow execution to confirm it runs successfully with the Node.js 24 runtime
- Consider pinning to specific version (optional Nit) - For production CI/CD, consider pinning to
@v5.0.0instead of@v5to prevent unexpected breaking changes from future v5.x releases
General findings
No issues identified. The change is minimal, well-scoped, and the v5 release notes indicate no breaking changes that would affect this repository's usage pattern. The Node.js 24 runtime upgrade is internal to the action execution environment and doesn't impact the workflow configuration.
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. This is a routine dependency update that brings in the latest version of the release automation tooling.
Verdict: Ready to approve - The change is minimal and low-risk.
Research notes
I reviewed the release-please-action v5.0.0 changelog:
- v5.0.0 (April 2026): Single breaking change - upgraded to Node 24 runtime. This is internal to the action and doesn't affect the API surface (inputs/outputs remain the same).
- The workflow uses manifest-based configuration (
config-file,manifest-file), which has been stable since v4.0.0 and continues to work identically in v5. - Bug fixes in v5 include bumping release-please from 17.3.0 to 17.6.0.
The current workflow configuration is fully compatible with v5:
- uses: googleapis/release-please-action@v5
with:
config-file: release-please-config.json
manifest-file: .release-please-manifest.json
token: ${{ secrets.RELEASE_TOKEN }}No migration steps are required beyond updating the version tag.
Suggested next steps
- Merge this PR to keep the release automation tooling up to date.
- Monitor the next release-please run to confirm the workflow executes correctly (standard practice for any CI/CD change).
General findings
None - this is a clean, well-scoped dependency update with no identified issues.
There was a problem hiding this comment.
Summary
This PR upgrades the release-please-action GitHub Action from v4 to v5. According to the official v5.0.0 release notes, the only breaking change is an upgrade to the Node 24 runtime, which is fully compatible with GitHub Actions' ubuntu-latest runner.
Verdict: Ready to merge - No configuration changes required.
Research Notes
- v5.0.0 changelog: Single breaking change is Node 24 runtime upgrade; includes bug fix bumping release-please core from 17.3.0 to 17.6.0
- Current workflow config: Uses manifest-based configuration (
config-file: release-please-config.json,manifest-file: .release-please-manifest.json), which remains unchanged and fully supported in v5 - Node 24 compatibility: GitHub Actions
ubuntu-latestrunners provide Node 24 by default, so no runner updates needed
Suggested Next Steps
- Merge this PR - no additional changes required
- Optionally monitor the next release-please workflow run to confirm successful execution
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 breaking changes for the current configuration.
Verdict: Ready to approve — the change is minimal and safe.
Research notes
Fetched the v5.0.0 release notes:
- Breaking change: upgrades to Node 24 runtime (handled transparently by GitHub Actions)
- Includes bug fixes from release-please 17.3.0 → 17.6.0
The repository README confirms the manifest-based configuration pattern used here (config-file, manifest-file) remains fully supported in v5.
Suggested next steps
- Merge this PR — no changes required.
- Optionally monitor the next release-please run to confirm expected behavior (standard practice for any CI/CD change).
General findings
None. The single-line change is correct and follows the project's existing dependency update pattern (see commit history showing previous renovate-managed updates).
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 managed by Renovate.
Verdict: Ready to approve - no changes required.
Research notes
Fetched the release-please-action v5.0.0 release notes:
- Breaking change: Upgrades to Node.js 24 runtime (internal to the action, no workflow changes needed)
- Bug fixes: Bumps underlying release-please from 17.3.0 to 17.6.0
The workflow configuration used here (manifest-based with config-file and manifest-file parameters) remains fully compatible with v5 per the official documentation.
Suggested next steps
- Merge this PR as-is - it's a safe, backward-compatible upgrade
- Monitor the next release-please run to confirm the action executes successfully (standard practice for any CI/CD change)
General findings
No issues identified. The change is minimal (single line), well-scoped, and follows the project's existing pattern for GitHub Actions versioning. The repository already uses recent versions of other actions (e.g., actions/checkout@v6, actions/setup-node@v6), so this aligns with the project's dependency management approach.
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 that brings the release automation tooling up to date.
Verdict: Ready to approve - no changes needed.
Research notes
Fetched the release-please-action v5.0.0 release notes:
- Breaking change: Upgrade to Node.js 24 runtime (internal to the action, no user-facing impact)
- Bug fixes: release-please core bumped from 17.3.0 to 17.6.0
The repository's current configuration uses the manifest-based approach (config-file: release-please-config.json and manifest-file: .release-please-manifest.json), which is the recommended pattern for v5 and remains fully compatible.
Suggested next steps
- Merge this PR to keep the release tooling current
- Monitor the next release-please run to confirm successful execution (standard practice for any CI/CD change)
General findings
No issues identified. The change is minimal (single line), well-scoped, and follows the project's existing patterns for GitHub Actions version management.
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 update that aligns with the latest stable version of the release-please action (v5.0.0 was released on Apr 22, 2026).
Verdict: Approved - This is a safe, routine maintenance update with no breaking changes affecting this repository's configuration.
Research notes
I fetched the release-please-action repository page and its CHANGELOG.md to understand what changed between v4 and v5:
Key findings from v5.0.0 changelog:
-
Breaking change: The only breaking change in v5.0.0 is "upgrade to node24" - this means the action now runs on Node.js 24 runtime. This is transparent to users since the action runs in GitHub's infrastructure, not on the repository's codebase.
-
Bug fixes: v5.0.0 includes a bump of release-please from 17.3.0 to 17.6.0, which brings bug fixes from the underlying release-please library.
-
Configuration compatibility: The repository uses manifest-based configuration (
config-file: release-please-config.jsonandmanifest-file: .release-please-manifest.json), which has been the recommended approach since v4.0.0 and remains unchanged in v5. -
No API changes: The action inputs used in this workflow (
config-file,manifest-file,token) remain supported in v5.
Version history context:
- v4.0.0 (Dec 2023) introduced major breaking changes including rewriting in TypeScript, removing the
commandoption, and consolidating configuration into manifest files - This repo already uses the manifest configuration pattern introduced in v4, so it's well-positioned for the v5 upgrade
- All v4.x releases between v4.0.0 and v4.4.1 were backward-compatible incremental updates
Suggested next steps
- Merge this PR - The update is safe and brings bug fixes from the underlying release-please library
- Monitor the first release run - After merging, watch the first execution of the release-please workflow to confirm it runs successfully on the new runtime
- Consider pinning to a specific minor version - For additional stability, consider using
@v5.0.0instead of@v5to avoid automatic jumps to future v5.x versions (optional, depends on your risk tolerance)
General findings
No issues identified. The change is minimal (single line), well-scoped, and follows best practices for GitHub Actions version management. The repository's existing manifest-based configuration (release-please-config.json with rust release type and cargo-workspace plugin) is fully compatible with v5.
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 workflow file.
Verdict: Ready to merge — no issues identified.
Research notes
Fetched the v5.0.0 release notes:
- Breaking change: Runtime upgraded to Node 24 (no impact on workflow configuration)
- Bug fixes: Internal release-please bumped from 17.3.0 to 17.6.0
- No configuration changes required for manifest-based releases
The current workflow uses:
- Manifest config (
release-please-config.json,.release-please-manifest.json) - Standard permissions (
contents: write,pull-requests: write,issues: write) - Custom token via
${{ secrets.RELEASE_TOKEN }}
All of these remain fully supported in v5.
Suggested next steps
- Merge as-is — this is a routine dependency update with no code changes required.
- After merging, monitor the next release cycle to confirm the action runs successfully (standard practice for any CI/CD change).
General findings
None — the change is minimal and low-risk.
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 — this is a routine, low-risk dependency update.
Research notes
Fetched the release-please-action v5.0.0 release notes:
- Breaking change: Upgrades to Node.js 24 runtime — this is internal to the action and requires no workflow changes
- Bug fixes: Updates release-please from 17.3.0 to 17.6.0
- The action's inputs (
token,config-file,manifest-file) remain unchanged and fully backward compatible
The current workflow configuration using manifest-based releases (release-please-config.json + .release-please-manifest.json) is the recommended approach and continues to work without modification.
Suggested next steps
- Merge this PR (no additional changes required)
- Consider enabling Dependabot auto-merge for patch/minor action updates if not already configured
General findings
None — this is a clean, well-scoped dependency update with no identified issues.
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 update in .github/workflows/release-please.yaml.
Verdict: Ready to approve - this is a low-risk dependency update with no breaking changes affecting the current configuration.
Research notes
- Fetched the release-please-action repository and CHANGELOG.md
- v5.0.0 breaking change: Upgrade to Node 24 runtime (internal to the action, no workflow changes required)
- v5.0.0 bug fixes: Includes release-please bump from 17.3.0 to 17.6.0
- The current workflow uses manifest-based configuration (
config-fileandmanifest-fileparameters), which is the recommended approach since v4 and remains unchanged in v5 - GitHub Actions best practice recommends using major version tags (
@v5) for automatic minor/patch updates while respecting semantic versioning
Suggested next steps
- Merge this PR - the update is safe and follows dependency update best practices
- Consider enabling Dependabot or Renovate for automatic GitHub Actions updates if not already configured
General findings
No issues found. The change is minimal, well-scoped, and the v5 upgrade maintains backward compatibility with the existing workflow configuration.
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. The change is a single-line version bump in .github/workflows/release-please.yaml.
Verdict: Ready to approve — this is a straightforward, low-risk dependency update with no breaking changes affecting the current configuration.
Research notes
- v5.0.0 release notes (source): The only breaking change is the upgrade to Node 24. GitHub's ubuntu-latest runners support Node 24, so this has no impact on workflow execution.
- v5 changes: Includes a bug fix bumping
release-pleasefrom 17.3.0 to 17.6.0 internally. No changes to action inputs or outputs that would affect this workflow. - Current configuration: The workflow uses manifest-based configuration (
config-file: release-please-config.json,manifest-file: .release-please-manifest.json), which is the recommended approach and remains fully compatible with v5.
Suggested next steps
- Merge this PR — no additional changes required.
- Optionally verify the first v5-triggered release PR creates correctly (standard due diligence for any release automation change).
General findings
None. The change is minimal, well-scoped, and the upstream documentation confirms backward compatibility for the configuration pattern in use.
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 minimal (single line) and represents a routine dependency upgrade.
Verdict: Ready to approve - no concerns identified.
Research notes
- Fetched release-please-action repository page and CHANGELOG.md
- v5.0.0 breaking change: Only "upgrade to node24" - this is an internal runtime change for the action, not affecting workflow configuration
- v5.0.0 bug fixes: Includes release-please bump from 17.3.0 to 17.6.0
- The current workflow uses manifest-based configuration (
config-file,manifest-file), which has been the standard approach since v4.0.0 and remains fully compatible with v5 - No other files in the repo reference
release-please-action, so this is an isolated change
Suggested next steps
- Merge as-is - this is a low-risk dependency update with no configuration changes required
- After merging, monitor the next release-please run to confirm expected behavior (standard practice for any CI/CD change)
General findings
None - the change is straightforward and correctly implemented.
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. This is a routine dependency update generated by Renovate.
Verdict: Approved — safe to merge.
Research notes
I reviewed the v5.0.0 release notes for release-please-action:
- Breaking change: Upgrade to Node 24 runtime (internal to the action implementation)
- Bug fixes: Bumps underlying
release-pleasefrom 17.3.0 to 17.6.0
The breaking change is purely internal to how the action runs — it does not affect the action's input/output interface. The current workflow configuration uses:
config-file: release-please-config.jsonmanifest-file: .release-please-manifest.jsontoken: ${{ secrets.RELEASE_TOKEN }}
All of these inputs remain supported in v5 per the official documentation. No migration steps are required for this configuration.
Suggested next steps
- Merge this PR — no changes required.
- After merge, monitor the next release PR creation to confirm the action runs successfully (standard practice for any CI/CD dependency update).
General findings
No issues identified. This is a straightforward, low-risk dependency update.
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 workflow file. Based on my review of the v5.0.0 release notes, the only breaking change is an internal upgrade to Node.js 24 runtime, which does not affect the action's configuration or behavior. The workflow uses manifest-based configuration which remains fully compatible.
Verdict: Ready to approve - this is a safe, routine dependency update.
Research notes
- Fetched release-please-action v5.0.0 release notes: Breaking change is "upgrade to node24" - an internal runtime update that doesn't affect action inputs/outputs
- Fetched CHANGELOG.md: v5 also includes bug fix bumping release-please from 17.3.0 to 17.6.0
- Verified current workflow configuration uses manifest mode (
config-file,manifest-file) which is the default and unchanged behavior since v4 - Confirmed all used inputs (
token,config-file,manifest-file) remain supported in v5 per the README
Suggested next steps
- Merge this PR - no changes required. The update is safe and brings bug fixes from the underlying release-please library.
General findings
None - this is a clean, low-risk dependency update with no identified issues.
There was a problem hiding this comment.
Summary
This PR updates googleapis/release-please-action from v4 to v5. The upgrade is straightforward—the only breaking change is the internal Node 24 runtime upgrade, which is fully compatible with GitHub's ubuntu-latest runner (Ubuntu 24.04). All configuration options used in the workflow (config-file, manifest-file, token) remain unchanged and supported.
Verdict: Ready to approve—no changes required.
Research Notes
- v5.0.0 Release Notes: Confirms Node 24 upgrade as the sole breaking change, plus release-please core bumped from 17.3.0 to 17.6.0
- Action README: Documents all input parameters; none of the parameters used in this workflow were changed or deprecated
- Runner Images:
ubuntu-latest= Ubuntu 24.04, which supports Node 24
Suggested Next Steps
- Merge this PR as-is—no modifications needed.
- Optionally verify the release-please workflow runs successfully after merge (standard practice for any CI/CD change).
General Findings
No issues identified. This is a low-risk, routine dependency update maintained by Renovate. The action is an official Google-maintained action with proper semantic versioning, and v5 represents a clean major version bump driven by the Node runtime upgrade rather than any functional breaking changes to the action's interface.
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
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.