chore(deps): bump googleapis/release-please-action from 4.4.1 to 5.0.0

[dependabot]

Bumps googleapis/release-please-action from 4.4.1 to 5.0.0.

Release notes

Sourced from googleapis/release-please-action's releases.

v5.0.0

5.0.0 (2026-04-22)

⚠ 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)

Changelog

Sourced from googleapis/release-please-action's changelog.

Changelog

5.0.0 (2026-04-22)

⚠ 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)

4.4.1 (2026-02-20)

Bug Fixes

• bump release-please from 17.1.3 to 17.3.0 (#1183) (ef9c274)

4.4.0 (2025-10-09)

Features

• add ability to select versioning-strategy and release-as (#1121) (ee0f5ba)

Bug Fixes

• changelog-host parameter ignored when using manifest configuration (#1151) (535c413)
• bump mocha from 11.7.1 to 11.7.2 in the npm_and_yarn group across 1 directory (#1149) (3612a99)
• bump release-please from 17.1.2 to 17.1.3 (#1158) (66fbfe9)

4.3.0 (2025-08-20)

Features

• deps: update release-please to 17.1.2 (f07192c)

4.2.0 (2025-03-07)

Features

... (truncated)

Commits

• 45996ed chore(main): release 5.0.0 (#1200)
• a8121b9 chore: build dist (#1201)
• f533c26 fix: bump release-please from 17.3.0 to 17.6.0 (#1199)
• 46dfc01 feat!: upgrade to node24 (#1188)
• See full diff in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spotuify	Ready	Preview, Comment	Jun 11, 2026 11:31pm

[bhekanik]

Deferring for a maintainer. release-please-action v4→v5 is a major bump on the release pipeline (.github/workflows/release-please.yml) with breaking config/runtime changes; a bad merge here can silently break releases. This needs deliberate verification against the current release-please config (the automated release flow), not a batch merge — and merging workflow changes here needs a token with workflow scope. Leaving open with this note.