Skip to content

chore(deps): replace google-github-actions/release-please-action action with googleapis/release-please-action v3 - #275

Open
team-github-bot wants to merge 1 commit into
mainfrom
renovate/google-github-actions-release-please-action-replacement
Open

chore(deps): replace google-github-actions/release-please-action action with googleapis/release-please-action v3#275
team-github-bot wants to merge 1 commit into
mainfrom
renovate/google-github-actions-release-please-action-replacement

Conversation

@team-github-bot

@team-github-bot team-github-bot commented May 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
google-github-actions/release-please-actiongoogleapis/release-please-action action replacement v3v3

This is a special PR that replaces google-github-actions/release-please-action with the community suggested minimal stable replacement version.


Configuration

📅 Schedule: (in timezone Australia/Brisbane)

  • 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 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.


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

This PR has been generated by Mend Renovate CLI.

@team-github-bot
team-github-bot requested a review from a team as a code owner May 7, 2026 23:33
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch 3 times, most recently from a01786b to 1189eb9 Compare May 12, 2026 04:43
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch from 1189eb9 to c07a169 Compare May 28, 2026 04:55
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch from c07a169 to 70897bf Compare June 19, 2026 05:15
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch 2 times, most recently from 0d717d0 to dbe68a6 Compare June 30, 2026 04:52
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch 2 times, most recently from ccb032c to a73b86e Compare July 10, 2026 04:46
@team-github-bot

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: .github/workflows/release-please.yml
Command failed: /bin/sh -c npm install && npm run build
/bin/sh: 1: npm: not found

File name: .github/workflows/release-please.yml
Command failed: /bin/sh -c npm install && npm run build
/bin/sh: 1: npm: not found

@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch 5 times, most recently from 992e3fc to f4d4581 Compare July 28, 2026 04:33
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch from f4d4581 to 50c6aba Compare August 10, 2026 04:07
@team-github-bot
team-github-bot force-pushed the renovate/google-github-actions-release-please-action-replacement branch from 50c6aba to 154cc7d Compare August 12, 2026 04:14
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.

2 participants