You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent commits introduced a breaking change that appears undocumented.
Breaking Changes
1. imperva_cloud_waf dropped previously supported Kibana versions without migration guidance
Commit(s):af30af344a PR:#19013 What broke: The package compatibility constraint was raised from ^8.16.5 || ^9.0.0 to ^8.19.0 || ^9.0.0, which blocks install/upgrade for users on Kibana 8.16.x-8.18.x.
Evidence:
Before this commit (af30af3^): packages/imperva_cloud_waf/manifest.yml line 11 had:
version: "^8.16.5 || ^9.0.0"
After this commit (af30af3): packages/imperva_cloud_waf/manifest.yml:11 is:
version: "^8.19.0 || ^9.0.0"
packages/imperva_cloud_waf/changelog.yml:2-6 (v1.13.2) only documents a CEL bugfix and does not mention a compatibility-floor change.
Why undocumented: No explicit breaking-change or migration note was found in the changelog entry or PR description for this compatibility drop.
Suggested fix: Add a breaking-change note and migration guidance in packages/imperva_cloud_waf/changelog.yml and package docs/PR notes, explicitly listing unsupported stack versions and upgrade path.
Suggested Actions
Document the Kibana compatibility drop for imperva_cloud_waf 1.13.2
Add migration guidance for users on Kibana 8.16.x-8.18.x
Note
🔒 Integrity filter blocked 10 items
The following items were blocked because they don't meet the GitHub integrity level.
#18819search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19182search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19013search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19118search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18951search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19186search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#18844search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#16918search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19179search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#19169search_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:
Recent commits introduced a breaking change that appears undocumented.
Breaking Changes
1.
imperva_cloud_wafdropped previously supported Kibana versions without migration guidanceCommit(s):
af30af344aPR: #19013
What broke: The package compatibility constraint was raised from
^8.16.5 || ^9.0.0to^8.19.0 || ^9.0.0, which blocks install/upgrade for users on Kibana8.16.x-8.18.x.Evidence:
af30af3^):packages/imperva_cloud_waf/manifest.ymlline 11 had:version: "^8.16.5 || ^9.0.0"af30af3):packages/imperva_cloud_waf/manifest.yml:11is:version: "^8.19.0 || ^9.0.0"packages/imperva_cloud_waf/changelog.yml:2-6(v1.13.2) only documents a CEL bugfix and does not mention a compatibility-floor change.Why undocumented: No explicit breaking-change or migration note was found in the changelog entry or PR description for this compatibility drop.
Suggested fix: Add a breaking-change note and migration guidance in
packages/imperva_cloud_waf/changelog.ymland package docs/PR notes, explicitly listing unsupported stack versions and upgrade path.Suggested Actions
imperva_cloud_waf1.13.2Note
🔒 Integrity filter blocked 10 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Breaking Change Detector
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.