-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssi_all: update Kibana version constraint to support 9.0 #12919
ssi_all: update Kibana version constraint to support 9.0 #12919
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified no package from #11775 (comment) is added to this PR.
@@ -1,4 +1,9 @@ | |||
# newer versions go on top | |||
- version: "1.32.0" | |||
changes: | |||
- description: Update Kibana constraint to support 9.0.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- description: Update Kibana constraint to support 9.0.0. | |
- description: Add Kibana constraint to support 9.0.0. |
Its better to have this changelog, since we are not updating, but adding 9.0.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The kibana constraint is being modified to add the 9.0.0 semver clause. I think update matches this.
Have we run the CI against 9.0.0 ? |
The daily 9.0.0-SNAPSHOT tests do run against 9. |
It should be possible to trigger a test of a specific stack version via comment
|
Yes thats how we also tested /test stack 9.0.0-SNAPSHOT |
That would not run for these PR's I suppose. |
Yeah, it would not run against these, but the tests that would run are functionally identical since these changes all only change the changelog and the |
/test stack 9.0.0-SNAPSHOT |
💚 Build Succeeded
|
Failure is unrelated flake:
@jsoriano Do you have any idea why this happens (I think I've seen it before). |
/test stack 9.0.0-SNAPSHOT |
Package ti_abusech - 2.6.0 containing this change is available at https://epr.elastic.co/package/ti_abusech/2.6.0/ |
Package ti_cif3 - 1.17.0 containing this change is available at https://epr.elastic.co/package/ti_cif3/1.17.0/ |
Package ti_crowdstrike - 2.4.0 containing this change is available at https://epr.elastic.co/package/ti_crowdstrike/2.4.0/ |
Package ti_cybersixgill - 1.33.0 containing this change is available at https://epr.elastic.co/package/ti_cybersixgill/1.33.0/ |
Package ti_domaintools - 0.2.0 containing this change is available at https://epr.elastic.co/package/ti_domaintools/0.2.0/ |
Package ti_eclecticiq - 1.4.0 containing this change is available at https://epr.elastic.co/package/ti_eclecticiq/1.4.0/ |
Package ti_eset - 1.6.0 containing this change is available at https://epr.elastic.co/package/ti_eset/1.6.0/ |
Package ti_maltiverse - 1.5.0 containing this change is available at https://epr.elastic.co/package/ti_maltiverse/1.5.0/ |
Package ti_mandiant_advantage - 1.9.0 containing this change is available at https://epr.elastic.co/package/ti_mandiant_advantage/1.9.0/ |
Package ti_misp - 1.38.0 containing this change is available at https://epr.elastic.co/package/ti_misp/1.38.0/ |
Package ti_opencti - 2.6.0 containing this change is available at https://epr.elastic.co/package/ti_opencti/2.6.0/ |
Package ti_otx - 1.28.0 containing this change is available at https://epr.elastic.co/package/ti_otx/1.28.0/ |
Package ti_rapid7_threat_command - 2.4.0 containing this change is available at https://epr.elastic.co/package/ti_rapid7_threat_command/2.4.0/ |
Package ti_recordedfuture - 1.29.0 containing this change is available at https://epr.elastic.co/package/ti_recordedfuture/1.29.0/ |
Package ti_threatconnect - 1.8.0 containing this change is available at https://epr.elastic.co/package/ti_threatconnect/1.8.0/ |
Package ti_threatq - 1.31.0 containing this change is available at https://epr.elastic.co/package/ti_threatq/1.31.0/ |
Package ti_util - 1.7.0 containing this change is available at https://epr.elastic.co/package/ti_util/1.7.0/ |
Package tines - 1.15.0 containing this change is available at https://epr.elastic.co/package/tines/1.15.0/ |
Package trellix_edr_cloud - 1.7.0 containing this change is available at https://epr.elastic.co/package/trellix_edr_cloud/1.7.0/ |
Package trellix_epo_cloud - 1.15.0 containing this change is available at https://epr.elastic.co/package/trellix_epo_cloud/1.15.0/ |
Package trend_micro_vision_one - 1.26.0 containing this change is available at https://epr.elastic.co/package/trend_micro_vision_one/1.26.0/ |
Package trendmicro - 2.7.0 containing this change is available at https://epr.elastic.co/package/trendmicro/2.7.0/ |
Package tychon - 0.3.0 containing this change is available at https://epr.elastic.co/package/tychon/0.3.0/ |
Package vectra_detect - 1.13.0 containing this change is available at https://epr.elastic.co/package/vectra_detect/1.13.0/ |
Package websocket - 0.2.0 containing this change is available at https://epr.elastic.co/package/websocket/0.2.0/ |
Package zerofox - 1.28.0 containing this change is available at https://epr.elastic.co/package/zerofox/1.28.0/ |
Package zeronetworks - 1.18.0 containing this change is available at https://epr.elastic.co/package/zeronetworks/1.18.0/ |
Package zoom - 1.22.0 containing this change is available at https://epr.elastic.co/package/zoom/1.22.0/ |
Package zscaler_zpa - 1.21.0 containing this change is available at https://epr.elastic.co/package/zscaler_zpa/1.21.0/ |
Proposed commit message
Updated minor version and Kibana constraints to support 9.0 for all packages owned by the Security Service Integrations team, except for the ones already updated at #12593, and the ones listed at #11775 which are still pending for some breaking changes.
Checklist
changelog.yml
file.Related issues