[axonius] Updated kibana version to reflect ILM policy delete index feature.

[muskan-agarwal26]

Proposed commit message

1. Update in kibana version to support the latest release versions to execute the ILM policy delete step.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Relates [9.4] [Axonius] - Fix Cannot execute ILM policy delete step (#149797) elasticsearch#150846
• Relates [8.19] [Axonius] - Fix Cannot execute ILM policy delete step (#149797) elasticsearch#150609
• Relates [9.3] [Axonius] - Fix Cannot execute ILM policy delete step (#149797) elasticsearch#150605

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[github-actions]

TL;DR

Buildkite failed before tests ran because the PR could not auto-merge with main during the checkout hook. The conflict is in packages/axonius/changelog.yml, where both branches define a top 0.1.1 release entry.

Remediation

• Rebase the PR branch onto latest main and resolve packages/axonius/changelog.yml by keeping the existing 0.1.1 entry from main and adding this PR as a new top entry (typically 0.1.2) with the Kibana version update note.
• Ensure packages/axonius/manifest.yml and packages/axonius/changelog.yml are consistent (manifest package version should match the new changelog top version), then push the rebase.
• Re-run CI; this failure is in pipeline upload/merge preparation, so it should clear once the conflict is resolved.

Investigation details

Root Cause

repository post-checkout attempts to create a merge branch (pr_merge_19440) and merge PR head into current main. That merge fails due to a content conflict in:

• packages/axonius/changelog.yml

The PR head has:

• version: 0.1.1 with description "Update in kibana version." and link to #19440

Current main also has:

• version: 0.1.1 with description "Fix use of orValue on non-optional specific_data field access in asset CEL programs." and link to #19445

Because both changed the same top block at the same version key, Buildkite’s pre-build merge step stops before any downstream jobs.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44300
• Job/step: :pipeline::arrow_up: Upload Pipeline: .buildkite/pipeline.yml
• Key log excerpt:
  • CONFLICT (content): Merge conflict in packages/axonius/changelog.yml
  • Automatic merge failed; fix conflicts and then commit the result.
  • Merge failed: 1
  • Error: running "repository post-checkout" shell hook

Verification

• Not run locally; diagnosis is based on Buildkite checkout hook output and direct comparison of PR-head vs main file content.

Follow-up

After rebasing, if CI still fails, share the new Buildkite failed step/log and I can triage the next blocker.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• #19440 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [axonius] Updated kibana version to reflect ILM policy delete index feature. #19440 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

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

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 09a8395

History

• 💔 Build #44300 failed 8356caf
• 💔 Build #44272 failed e60a25b

[kcreddy]

The versions are not public yet. See https://www.elastic.co/blog

Latest releases:

[kcreddy]

See #19440 (comment)