Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

Is this change needed? (asked in the meta issue too #2363 (comment))

Is this change needed? (asked in the meta issue too #2363 (comment))

Hmm .. I thought since this is a major version change and has breaking changes compared to ECS 1.12 it might be easier to update all packages to the next major version (8.0) that way any future modifications to the package work in 8.0. Also in some cases there were documentation updates to fields.

Is this change needed? (asked in the meta issue too #2363 (comment))

Hmm .. I thought since this is a major version change and has breaking changes compared to ECS 1.12 it might be easier to update all packages to the next major version (8.0) that way any future modifications to the package work in 8.0. Also in some cases there were documentation updates to fields.

It is still not clear to me why this change was needed in packages like this one that don't use any of the modified fields. 🤔

Breaking changes are mentioned, do these breaking changes somehow affect this package? (Should it be indicated in the changelog? The version be upgraded to 2.x? The kibana constraints changed?...)