Skip to content

chore(deps): Bump release-plz/action from 0.5.128 to 0.5.129#44

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/release-plz/action-0.5.129
Open

chore(deps): Bump release-plz/action from 0.5.128 to 0.5.129#44
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/release-plz/action-0.5.129

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 10, 2026

Bumps release-plz/action from 0.5.128 to 0.5.129.

Release notes

Sourced from release-plz/action's releases.

v0.5.129

What's Changed

... (truncated)

Commits
  • 064f4d1 chore(deps): update dependency obi1kenobi/cargo-semver-checks to v0.47 (#397)
  • 4f2dca0 fix cargo-semver-checks renovate update (#396)
  • 39f5787 Update to 0.3.158 (#395)
  • bb36e14 chore(deps): update dependency taiki-e/install-action to v2.77.4 (#394)
  • 3711471 chore(deps): update dependency taiki-e/install-action to v2.77.3 (#393)
  • b234371 chore(deps): update dependency taiki-e/install-action to v2.77.2 (#392)
  • 3427ba6 chore(deps): update dependency cargo-bins/cargo-binstall to v1.19.1 (#391)
  • 37e90aa chore(deps): update dependency taiki-e/install-action to v2.77.1 (#390)
  • eef2a46 chore(deps): update dependency taiki-e/install-action to v2.77.0 (#389)
  • eb60137 chore(deps): update dependency taiki-e/install-action to v2.76.0 (#388)
  • 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.128 to 0.5.129.
- [Release notes](https://github.com/release-plz/action/releases)
- [Commits](release-plz/action@1528104...064f4d1)

---
updated-dependencies:
- dependency-name: release-plz/action
  dependency-version: 0.5.129
  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 May 10, 2026
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label May 10, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 10, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 CI must pass

Wonderful, this rule succeeded.

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

Wonderful, this rule succeeded.

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

  • #commits-behind <= 3

Copy link
Copy Markdown
Contributor

@mergify mergify Bot left a comment

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 added the queued label May 10, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 10, 2026

Merge Queue Status

This pull request spent 1 minute 5 seconds in the queue, including 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-or-neutral = compat (1.85.0)
  • check-success-or-neutral = compat (stable minus 2 releases)
  • check-success-or-neutral = compat (stable minus 5 releases)
  • check-success-or-neutral = compat (stable)
  • check-success-or-neutral = fuzz (fuzz_map_file)
  • check-success-or-neutral = fuzz (fuzz_read_bounded)
  • 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
  • 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-or-neutral = compat (1.85.0)
  • check-success-or-neutral = compat (stable minus 2 releases)
  • check-success-or-neutral = compat (stable minus 5 releases)
  • check-success-or-neutral = compat (stable)
  • check-success-or-neutral = fuzz (fuzz_map_file)
  • check-success-or-neutral = fuzz (fuzz_read_bounded)
  • all of [🛡 Merge Protections rule CI must pass]:
    • 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 = quality
  • check-success = quality
  • all of [🛡 Merge Protections rule Do not merge outdated PRs]:
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

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.

mergify Bot added a commit that referenced this pull request May 10, 2026
@mergify mergify Bot added dequeued and removed queued labels May 10, 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 dequeued 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