chore(deps): update googleapis/release-please-action action to v5

[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 (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)

v5.0

Compare Source

v5

Compare Source

---

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 in the release workflow. This is a routine dependency update that brings in the latest release-please functionality.

Verdict: Ready to approve - This is a low-risk, well-scoped dependency update with no breaking changes affecting the current workflow configuration.

Research notes

I reviewed the release-please-action repository and its CHANGELOG.md:

• v5.0.0 (released April 22, 2026) contains one breaking change: upgrade to Node 24 runtime. This is internal to the action and doesn't affect how it's invoked or configured.
• The changelog shows bug fixes including bumping release-please from 17.3.0 to 17.6.0
• No input/output API changes between v4 and v5 that would impact this workflow
• The workflow already uses the recommended manifest-based configuration (config-file and manifest-file), which remains unchanged

Suggested next steps

1. Merge this PR - The update is safe and follows best practices for keeping GitHub Actions dependencies current
2. Monitor the first release - After merging, watch the next release workflow run to confirm successful execution (standard practice for any CI/CD change)

General findings

No issues found. The change is minimal, well-understood, and follows the pattern established by the upstream maintainers:

• Single line change in .github/workflows/release-please.yml
• Uses semantic versioning tag (@v5) consistent with GitHub Actions best practices
• Workflow configuration remains compatible (manifest-based approach)
• No other files require updates