[breaking-change] Undocumented breaking changes detected (2026-05-28)

[github-actions]

Recent commits introduced a breaking change that appears undocumented.

Breaking Changes

1. osquery_manager raised minimum Kibana requirement without migration note

Commit(s): 7000d19311
PR: #18989
What broke: osquery_manager compatibility changed from Kibana ^9.4.0 to ^9.4.2, which drops support for 9.4.0 and 9.4.1. Consumers pinned to those versions can no longer use package 1.29.0.
Evidence:

• packages/osquery_manager/manifest.yml changed:
  • conditions.kibana.version: "^9.4.0" → "^9.4.2"
• packages/osquery_manager/changelog.yml for 1.29.0 only mentions ECS mapping generation and osquery 5.23.0 upgrade; no compatibility break or migration guidance.
  Why undocumented: PR title/body/comments and the package changelog do not document the Kibana floor increase or provide migration guidance for users on 9.4.0/9.4.1.
  Suggested fix: Add explicit release note/changelog text documenting the minimum Kibana version increase and migration guidance for affected users.

Suggested Actions

• Document the Kibana version floor increase (^9.4.0 → ^9.4.2) in release notes/changelog
• Add migration guidance for users on Kibana 9.4.0/9.4.1

Note

🔒 Integrity filter blocked 3 items

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

• #19232 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19254 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #18989 search_pull_requests: 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: Breaking Change Detector

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

• expires on Jun 4, 2026, 2:26 PM UTC