Skip to content

[breaking-change] Undocumented breaking changes detected (2026-06-03) #19361

Open

Description

@github-actions

Recent commits introduced a breaking compatibility change that appears undocumented.

Breaking Changes

1. Imperva Cloud WAF support range was narrowed without migration notice

Commit(s): b0facda208
PR: #18227
What broke: The package compatibility contract for Kibana was tightened from ^8.19.0 || ^9.0.0 to ^8.19.16 || ~9.3.5 || ^9.4.1, which drops previously supported versions (8.19.0-8.19.15, 9.0.0-9.3.4, and 9.4.0). Users on those versions can no longer install/upgrade this integration version.
Evidence:

  • packages/imperva_cloud_waf/manifest.yml (kibana condition changed in this commit)
  • Diff in commit b0facda208: conditions.kibana.version changed from ^8.19.0 || ^9.0.0 to ^8.19.16 || ~9.3.5 || ^9.4.1
    Why undocumented:
  • PR title/body describe agentless support, but do not call out the compatibility contraction or migration path.
  • packages/imperva_cloud_waf/changelog.yml entry for 1.14.0 only says "Enable Agentless deployment."
  • packages/imperva_cloud_waf/docs/README.md adds agentless details but no version-compatibility break notice.
    Suggested fix: Add explicit breaking-change note and migration guidance (minimum supported Kibana versions and upgrade path) in changelog/release notes and package docs.

Suggested Actions

  • Document this breaking compatibility change in changelog/release notes
  • Add migration guidance for users on now-unsupported Kibana versions

Note

🔒 Integrity filter blocked 17 items

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

  • #19209 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18337 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19218 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18621 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19276 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19259 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19293 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18503 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18552 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18525 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19071 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18227 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #13002 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #15147 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #14186 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #11952 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • ... and 1 more item

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 10, 2026, 2:47 PM UTC

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions