Skip to content

chore(deps): update module github.com/apparentlymart/go-textseg/v15 to v17 (9.4)#7339

Open
elastic-renovate-prod[bot] wants to merge 1 commit into
9.4from
renovate/9.4-github.com-apparentlymart-go-textseg-v15-17.x
Open

chore(deps): update module github.com/apparentlymart/go-textseg/v15 to v17 (9.4)#7339
elastic-renovate-prod[bot] wants to merge 1 commit into
9.4from
renovate/9.4-github.com-apparentlymart-go-textseg-v15-17.x

chore(deps): update module github.com/apparentlymart/go-textseg/v15 t…

0b9146b
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 20, 2026 in 5s

1 rule matches and 8 potential rules

Templating in comment.message beyond simple variables is deprecated and will be removed in a future release. Allowed variables: approvers, assignees, author, base, body, head, labels, number, queue_dequeue_reason, title.

Rule: auto-merge Renovate PRs (merge)

  • #approved-reviews-by>=1
  • check-success=Lint
  • github-review-approved [🛡 GitHub branch protection] (documentation)
  • github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate] (documentation)
  • github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR] (documentation)
  • label=renovate-auto-approve
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Lint
    • check-skipped = Lint
    • check-success = Lint
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author=elastic-renovate-prod[bot]
  • check-success=Manifest Tests
  • check-success=Package Cloudbeat (docker)
  • check-success=Package Cloudbeat (tar.gz)
  • check-success=Test Rego Policies
  • check-success=Unit Test
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Unit Test
    • check-neutral = Unit Test
    • check-skipped = Unit Test
  • any of: [🛡 GitHub branch protection]
    • check-success = Package Cloudbeat (docker)
    • check-neutral = Package Cloudbeat (docker)
    • check-skipped = Package Cloudbeat (docker)
  • any of: [🛡 GitHub branch protection]
    • check-success = Package Cloudbeat (tar.gz)
    • check-neutral = Package Cloudbeat (tar.gz)
    • check-skipped = Package Cloudbeat (tar.gz)

✅ Rule: self-assign PRs (assign)

  • #assignee=0
  • -closed
  • -merged

Rule: forward-port patches to main branch (backport)

  • label=forwardport-main
  • merged
  • merged [📌 backport requirement]

Rule: ask to resolve conflict (comment)

  • conflict
  • -closed
  • -merged

Rule: remove-backport label (label)

  • label~=backport-v
  • -closed
  • -merged

Rule: backport patches to 8.19 branch (backport)

  • label=backport-v8.19.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 9.3 branch (backport)

  • label=backport-v9.3.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 9.4 branch (backport)

  • label=backport-v9.4.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 9.5 branch (backport)

  • label=backport-v9.5.0
  • merged
  • merged [📌 backport requirement]
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

5 not applicable rules

Rule: close automated pull requests with bump updates if any conflict (close)

  • author=apmmachine
  • conflict
  • label=automation
  • -closed
  • -merged

Rule: automatic approval for mergify pull requests with changes in bump-rules (review)

  • author=mergify[bot]
  • check-success=Lint
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • check-success=Test Rego Policies
  • check-success=Unit Test

Rule: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified. (merge)

  • #approved-reviews-by>=1
  • check-success=Lint
  • files~=^\.mergify\.yml$
  • github-review-approved [🛡 GitHub branch protection] (documentation)
  • github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate] (documentation)
  • github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR] (documentation)
  • head~=^add-backport-next.*
  • label=automation
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Lint
    • check-skipped = Lint
    • check-success = Lint
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=Test Rego Policies
  • check-success=Unit Test
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Unit Test
    • check-neutral = Unit Test
    • check-skipped = Unit Test
  • any of: [🛡 GitHub branch protection]
    • check-success = Package Cloudbeat (docker)
    • check-neutral = Package Cloudbeat (docker)
    • check-skipped = Package Cloudbeat (docker)
  • any of: [🛡 GitHub branch protection]
    • check-success = Package Cloudbeat (tar.gz)
    • check-neutral = Package Cloudbeat (tar.gz)
    • check-skipped = Package Cloudbeat (tar.gz)

Rule: notify the backport has not been merged yet (comment)

  • #assignee>=1
  • author=mergify[bot]
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #check-success>0
  • -closed
  • -merged

Rule: notify the backport policy (comment)

  • -label~=^backport
  • base=main
  • -closed
  • -merged
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