Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/googleapis-release-please-action-5.x
Open

chore(deps): update googleapis/release-please-action action to v5#36
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/googleapis-release-please-action-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 23, 2026

This PR contains the following updates:

Package Type Update Change
googleapis/release-please-action action major v4v5

Release Notes

googleapis/release-please-action (googleapis/release-please-action)

v5.0.0

Compare Source

⚠ BREAKING CHANGES
Features
Bug Fixes

v5.0

Compare Source

v5

Compare Source

v4.4.1

Compare Source

v4.4.0

Compare Source

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)

v4.4

Compare Source

v4.3.0

Compare Source

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

v4.3

Compare Source

v4.2.0

Compare Source

Features
  • support for skip-labeling parameter for GitHub action (#​1066) (fb7f385)

v4.2

Compare Source

v4.1.5

Compare Source

Bug Fixes

v4.1.4

Compare Source

Bug Fixes

v4.1.3

Compare Source

Bug Fixes

v4.1.2

Compare Source

Bug Fixes

v4.1.1

Compare Source

Bug Fixes

v4.1.0

Compare Source

Features

v4.1

Compare Source

v4.0.3

Compare Source

Bug Fixes

v4.0.2

Compare Source

Bug Fixes

v4.0.1

Compare Source

Bug Fixes

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.

@renovate renovate Bot force-pushed the renovate/googleapis-release-please-action-5.x branch from fe84fe2 to 86108bf Compare April 30, 2026 02:41
@renovate renovate Bot force-pushed the renovate/googleapis-release-please-action-5.x branch from 86108bf to 7e4bd56 Compare May 13, 2026 04:10
Copy link
Copy Markdown

@doubleword-code doubleword-code Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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):).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants