ci(mergify): upgrade configuration to current format

[mergify]

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2026-07-31, otherwise your configuration will stop working.

What's Changed?

• queue_rules → conditions: conditions in queue rule configuration is deprecated. Use merge_conditions instead. (deadline: 2026-07-31)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: f98a236

Failed CI Steps

• Check integrations netbox
• Check integrations o365_metrics

History

[github-actions]

TL;DR

Check integrations netbox failed, but the provided job log only contains teardown/output-upload lines and not the actual failing command/test output. The PR itself only changes Mergify config (.mergify.yml) and does not touch packages/netbox, so this does not currently point to a code regression in this PR.

Remediation

• Re-run Check integrations netbox once (likely transient/incomplete log capture for this run).
• If it fails again, inspect and paste the failing section from the full step log (before teardown) or from uploaded test artifact build/test-results/netbox-system-*.xml so we can identify the exact assertion/stack trace.

Investigation details

Root Cause

Inconclusive from available data. The only supplied log (/tmp/gh-aw/buildkite-logs/integrations-check-integrations-netbox.txt) starts at stack teardown and ends with generic exit status.

The PR diff is limited to .mergify.yml (conditions → merge_conditions in queue rule), which is unrelated to NetBox package runtime/tests.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/42385
• Job/step: Check integrations netbox
• Key log excerpt:
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-netbox.txt:73 --- [netbox] failed
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-netbox.txt:76 Error: The command exited with status 1
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-netbox.txt:80 artifact upload begins immediately (no preceding failure stack/assert output in provided file)
• PR change scope:
  • .mergify.yml only (queue rule field rename), no packages/netbox changes.

Verification

• Not run locally: reproducing this Buildkite package pipeline step requires the CI test harness and stack context; analysis is based on provided failure logs and PR diff.

Follow-up

If a retry reproduces, share the first failing test/command block from the step log and I can map it directly to source lines with a concrete patch recommendation.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[mrodm]

Issue related to netbox is going to be fixed by this PR: #18679