[renovate]

This PR contains the following updates:

Package	Type	Update	Change
googleapis/release-please-action	action	major	v4 → v5

---

Release Notes

googleapis/release-please-action

v5.0.0

Compare Source

⚠ BREAKING CHANGES

• upgrade to node24 (#​1188)

Features

• upgrade to node24 (#​1188) (46dfc01)

Bug Fixes

• bump release-please from 17.3.0 to 17.6.0 (#​1199) (f533c26)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[doubleword-code]

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.yml. After reviewing the v5.0.0 changelog and the current workflow configuration, this update is safe to merge.

Verdict: Approved ✅

Research notes

Fetched the release-please-action repository page and CHANGELOG.md to understand the v4→v5 migration:

• v5.0.0 breaking change: "upgrade to node24" — this refers to the Node.js runtime version the action executes on internally (previously Node 20 in v4). This does not affect the action's input/output interface or require any workflow changes.
• No API changes: All inputs used in this repo (token, config-file, manifest-file) and outputs consumed (release_created, tag_name) remain unchanged between v4 and v5.
• Manifest configuration: The repo uses manifest-based configuration (via release-please-config.json and .release-please-manifest.json), which was introduced in v4 and continues to be the default mode in v5.

Suggested next steps

1. Merge this PR — no additional changes required
2. After merging, monitor the next release-please workflow run to confirm normal operation (this is standard practice for any dependency update)

General findings

None. The change is minimal, well-scoped, and follows the conventional commit format expected by release-please itself (chore(deps):).

[doubleword-code]

Summary

This PR upgrades the release-please GitHub Action from v4 to v5. The change is minimal (single line) and backwards-compatible with the repository's existing manifest-based configuration.

Verdict: Approve ✅

Research notes

Fetched the release-please-action repository and reviewed the v5.0.0 changelog:

• v5.0.0 (April 22, 2026) contains one breaking change: upgrade to Node.js 24 runtime
• The underlying release-please CLI was bumped from 17.3.0 to 17.6.0 in v5
• All action inputs remain compatible, including token, config-file, and manifest-file
• Output structure unchanged (release_created, tag_name, etc.)

The repository's current workflow configuration uses manifest-based releases (.release-please-manifest.json + release-please-config.json), which is the recommended approach and works identically in v4 and v5.

Suggested next steps

1. Merge this PR as-is — no changes needed
2. After merging, verify the next release cycle runs successfully on the new runtime (standard practice for any CI/CD dependency update)

General findings

None. The upgrade path is straightforward and the existing configuration requires no modifications.