Skip to content

chore(deps): Bump release-plz/action from 0.5.128 to 0.5.130 - #20

Merged
mergify[bot] merged 1 commit into
mainfrom
dependabot/github_actions/release-plz/action-0.5.130
Jun 24, 2026
Merged

chore(deps): Bump release-plz/action from 0.5.128 to 0.5.130#20
mergify[bot] merged 1 commit into
mainfrom
dependabot/github_actions/release-plz/action-0.5.130

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 24, 2026

Copy link
Copy Markdown
Contributor

Bumps release-plz/action from 0.5.128 to 0.5.130.

Release notes

Sourced from release-plz/action's releases.

v0.5.130

What's Changed

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

v0.5.129

What's Changed

... (truncated)

Commits
  • e879257 Update to 0.3.159 (#439)
  • 29ecf01 don't threat http 422 errors as special (#438)
  • c6756a4 chore(deps): update dependency cargo-bins/cargo-binstall to v1.20.0 (#437)
  • 0c186bf chore(deps): update dependency taiki-e/install-action to v2.81.8 (#436)
  • 8fe2bb5 chore(deps): lock file maintenance (#435)
  • 675b30f chore(deps): update dependency taiki-e/install-action to v2.81.7 (#433)
  • 7f61f63 chore(deps): update github actions to v6.0.3 (#385)
  • 7600366 chore(deps): update dependency taiki-e/install-action to v2.81.6 (#432)
  • f983e75 chore(deps): update dependency taiki-e/install-action to v2.81.5 (#431)
  • 02994ce chore(deps): update dependency taiki-e/install-action to v2.81.4 (#430)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jun 24, 2026
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jun 24, 2026
@mergify

mergify Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

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.
  • #commits-behind <= 3
  • check-success = Code Quality
  • check-success = Test (Windows)

🟢 🚦 Auto-queue

Wonderful, this rule succeeded.

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]
      • label = release
      • base = main

@mergify

mergify Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 5 minutes 18 seconds in the queue, with no time running CI.

Waiting for
  • check-success = Test (Windows)
  • check-success = Test (Windows)
All conditions
  • check-success = Test (Windows)
  • all of [🛡 Merge Protections rule CI must pass]:
  • check-success = Code Quality
  • 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

Pull request #20 has been dequeued

Queue conditions are not satisfied:

  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • all of: [🛡 Merge Protections rule CI must pass]
        • #commits-behind <= 3
      • any of: [🛡 GitHub repository ruleset rule main]
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections
        • check-success = Mergify Merge Protections

Failing checks:

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, 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 ↓.

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

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/release-plz/action-0.5.130 branch from 03c7ac0 to 66f9c04 Compare June 24, 2026 01:57
@mergify mergify Bot removed the queued label Jun 24, 2026
@mergify

mergify Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-06-24 02:00 UTC · Rule: default · triggered by merge protections
  • Checks skipped · PR is already up-to-date
  • Merged2026-06-24 02:01 UTC · at 66f9c041bd98bc96a3fcab1f069362d1046ddb9e · squash

This pull request spent 32 seconds in the queue, including 2 seconds running CI.

Required conditions to merge
  • check-success = Code Quality
  • check-success = Test (Windows)
  • all of [🛡 Merge Protections rule CI must pass]:
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections

mergify Bot added a commit that referenced this pull request Jun 24, 2026
@mergify
mergify Bot merged commit a9a9b9b into main Jun 24, 2026
11 checks passed
@dependabot
dependabot Bot deleted the dependabot/github_actions/release-plz/action-0.5.130 branch June 24, 2026 02:01
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