[breaking-change] Undocumented breaking changes detected (2026-06-11)

Recent commits introduced a breaking compatibility change that appears undocumented.

## Breaking Changes

### 1. Minimum supported Kibana versions were raised for three integrations without migration notes
**Commit(s):** [`da00eedb44`](https://github.com/elastic/integrations/commit/da00eedb442414d05f962ac72941e14909215382)
**PR:** https://github.com/elastic/integrations/pull/19479
**What broke:** Upgrading to the newest package versions now requires Kibana `^8.19.2 || ^9.0.5` for all three integrations below. Users on previously supported versions (`8.16.x/8.17.x/8.18.x/8.19.0-8.19.1` and `9.0.0-9.0.4`) can no longer install/upgrade to these new package versions.

**Evidence:**
- `packages/spycloud/manifest.yml` changed:
- `- version: "^8.16.0 || ^9.0.0"`
- `+ version: "^8.19.2 || ^9.0.5"`
- `packages/swimlane/manifest.yml` changed:
- `- version: "^8.17.4 || ^9.0.0"`
- `+ version: "^8.19.2 || ^9.0.5"`
- `packages/symantec_endpoint_security/manifest.yml` changed:
- `- version: "^8.16.5 || ^9.0.0"`
- `+ version: "^8.19.2 || ^9.0.5"`

**Why undocumented:**
- PR #19479 title/body describe adding agentless deployment, but do not call out the compatibility-floor increase or migration guidance.
- Changelog entries for the new versions only state `Enable Agentless deployment.` (enhancement) with no breaking-change note:
- `packages/spycloud/changelog.yml`
- `packages/swimlane/changelog.yml`
- `packages/symantec_endpoint_security/changelog.yml`
- README updates in the same commit add agentless explanation text only; they do not document this Kibana compatibility break.

**Suggested fix:**
- Add explicit breaking-change notes for these three packages (changelog/release notes/PR context).
- Include migration guidance for users pinned below `8.19.2` / `9.0.5` (for example, stack upgrade path or pinning previous package versions).

## Suggested Actions
- [ ] Document the Kibana minimum-version compatibility break for all three integrations
- [ ] Add migration guidance for affected users
- [ ] Ensure future compatibility-floor increases are called out as breaking changes

> [!NOTE]
>
> 🔒 Integrity filter blocked 2 items
>
> The following items were blocked because they don't meet the GitHub integrity level.
>
> - [#19347](https://github.com/elastic/integrations/pull/19347) `search_pull_requests`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#19479](https://github.com/elastic/integrations/pull/19479) `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:
>
> ```yaml
> tools:
> github:
> min-integrity: approved # merged | approved | unapproved | none
> ```
>
>

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Breaking Change Detector](https://github.com/elastic/integrations/actions/runs/27353394294)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Jun 18, 2026, 2:27 PM UTC