Skip to content

Update protobuf-java, protobuf-java-util to 4.27.2 #652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Merge branch 'master' into update/protobuf-java-4.27.2

9968f81
Select commit
Loading
Failed to load commit list.
Open

Update protobuf-java, protobuf-java-util to 4.27.2 #652

Merge branch 'master' into update/protobuf-java-4.27.2
9968f81
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 16, 2025 in 2s

1 rule matches and 3 potential rules

✅ Rule: label scala-steward's PRs (label)

  • author=scala-steward

Rule: merge Scala Steward's PRs (merge)

  • status-success=ci
  • any of: [🛡 GitHub branch protection]
    • check-neutral = ci
    • check-skipped = ci
    • check-success = ci
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author=scala-steward
  • base=master
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Summary
    • check-neutral = Summary
    • check-skipped = Summary

Rule: automatic merge for master when CI passes (delete_head_branch)

  • #approved-reviews-by>=1
  • closed [📌 delete_head_branch requirement]
  • label=mergify-merge
  • status-success=ci
  • base=master

Rule: automatic merge for master when CI passes (merge)

  • #approved-reviews-by>=1
  • label=mergify-merge
  • status-success=ci
  • any of: [🛡 GitHub branch protection]
    • check-neutral = ci
    • check-skipped = ci
    • check-success = ci
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=master
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Summary
    • check-neutral = Summary
    • check-skipped = Summary
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

View more details on Mergify