Skip to content

chore(deps): Bump release-plz/action from 0.5.130 to 0.5.131#388

Merged
mergify[bot] merged 8 commits into
mainfrom
dependabot/github_actions/release-plz/action-0.5.131
Jul 21, 2026
Merged

chore(deps): Bump release-plz/action from 0.5.130 to 0.5.131#388
mergify[bot] merged 8 commits into
mainfrom
dependabot/github_actions/release-plz/action-0.5.131

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor

Bumps release-plz/action from 0.5.130 to 0.5.131.

Release notes

Sourced from release-plz/action's releases.

v0.5.131

What's Changed

Full Changelog: release-plz/action@v0.5...v0.5.131

Commits
  • 2eb1d8b Update to 0.3.160 (#466)
  • bbdaa2c chore(deps): lock file maintenance (#465)
  • 77006e7 chore(deps): update dependency taiki-e/install-action to v2.83.2 (#464)
  • 4671811 chore(deps): update dependency taiki-e/install-action to v2.83.1 (#463)
  • 5825e6a chore(deps): update dependency taiki-e/install-action to v2.83.0 (#462)
  • 9627bb5 chore(deps): update dependency taiki-e/install-action to v2.82.11 (#461)
  • b291097 chore(deps): update dependency taiki-e/install-action to v2.82.10 (#460)
  • 3e68b2c chore(deps): lock file maintenance (#459)
  • 6ce0a80 chore(deps): update dependency taiki-e/install-action to v2.82.9 (#457)
  • 1ff444b chore(deps): update dependency taiki-e/install-action to v2.82.8 (#456)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [release-plz/action](https://github.com/release-plz/action) from 0.5.130 to 0.5.131.
- [Release notes](https://github.com/release-plz/action/releases)
- [Commits](release-plz/action@e879257...2eb1d8b)

---
updated-dependencies:
- dependency-name: release-plz/action
  dependency-version: 0.5.131
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 20, 2026
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jul 20, 2026
mergify[bot]
mergify Bot previously approved these changes Jul 20, 2026

@mergify mergify Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automatically approved by Mergify

@mergify

mergify Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 3 merge protections satisfied — ready to merge.

Show 3 satisfied protections

🟢 Full CI must pass

All CI checks must pass. Release-plz PRs are exempt because they only bump versions and changelogs (code was already tested on main), and GITHUB_TOKEN-triggered force-pushes suppress CI.

  • check-success = coverage
  • check-success = quality
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)

🟢 Do not merge outdated PRs

Make sure PRs are within 10 commits of the base branch before merging

  • #commits-behind <= 10

🟢 🚦 Auto-queue

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

  • any of:
    • all of:
      • author = dependabot[bot]
      • base = main
      • label != do-not-merge
    • all of:
      • author = dosubot[bot]
      • base = main
      • label != do-not-merge
    • all of:
      • author = release-plz[bot]
      • head ~= ^release-plz-
      • base = main
      • label != do-not-merge

@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 46 minutes 51 seconds in the queue, including 23 minutes 25 seconds running CI.

Waiting for
  • check-success = coverage
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)
  • check-success = coverage
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)
All conditions

Reason

The merge conditions cannot be satisfied due to failing checks

  • coverage
  • test
  • @dco/DCO
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

mergify[bot]
mergify Bot previously approved these changes Jul 21, 2026

@mergify mergify Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automatically approved by Mergify

@dependabot
dependabot Bot dismissed mergify[bot]’s stale review July 21, 2026 03:36

The merge-base changed after approval.

@mergify mergify Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automatically approved by Mergify

@mergify mergify Bot removed the queued label Jul 21, 2026
@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 43 minutes 38 seconds in the queue, including 22 minutes 39 seconds running CI.

Waiting for
  • check-success = coverage
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)
  • check-success = coverage
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)
All conditions

Reason

The merge conditions cannot be satisfied due to failing checks

  • coverage
  • test
  • @dco/DCO
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify mergify Bot removed the queued label Jul 21, 2026
@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 27 minutes 48 seconds in the queue, including 27 minutes 23 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Jul 21, 2026
@mergify
mergify Bot merged commit 3c5654c into main Jul 21, 2026
29 of 34 checks passed
@mergify
mergify Bot deleted the dependabot/github_actions/release-plz/action-0.5.131 branch July 21, 2026 04:59
@mergify mergify Bot removed the queued label Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants