[sharad-elastic]

Proposed commit message

Update changelog entry, manifest version and sync CODEOWNERS file with main branch.

[github-actions]

TL;DR

Check go sources failed because this PR changed the Barracuda CODEOWNERS entry to a team that does not match the package manifest owner. Update /packages/barracuda in .github/CODEOWNERS back to @elastic/security-service-integrations (or change packages/barracuda/manifest.yml owner to match, if intentional).

Remediation

• Change .github/CODEOWNERS entry for Barracuda from:
  • /packages/barracuda @elastic/integration-experience``
    to:
  • /packages/barracuda @elastic/security-service-integrations``
• Re-run CI (Check go sources) after the CODEOWNERS/manifest owner alignment.

Investigation details

Root Cause

dev/codeowners.Check validates that package owner in each manifest.yml exists in .github/CODEOWNERS for that package path.

At PR head (322568d9cb1463096e9b536c004fe6904fc29b4c):

• packages/barracuda/manifest.yml:63 has github: elastic/security-service-integrations
• .github/CODEOWNERS:147 has /packages/barracuda @elastic/integration-experience``

These are inconsistent, so validation fails.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/43307
• Job/step: ✅ Check go sources (.buildkite/scripts/check_sources.sh)
• Key log excerpt:

  Running dependency: github.com/elastic/integrations/dev/codeowners.Check
  Error: error validating packages in directory 'packages': error checking manifest 'packages/barracuda/manifest.yml': owner "elastic/security-service-integrations" defined in "packages/barracuda/manifest.yml" is not in ".github/CODEOWNERS"
  

• Commit diff evidence: parent commit had /packages/barracuda @elastic/security-service-integrations``; this PR changed it to @elastic/integration-experience.

Verification

• Not run in this environment: .buildkite/scripts/check_sources.sh depends on Buildkite runtime env vars (SETUP_GVM_VERSION), but failure is directly evidenced in the Buildkite log and the checked-in files at PR head.

Follow-up

• If Barracuda ownership was intentionally moved to Integration Experience, update packages/barracuda/manifest.yml owner accordingly in the same PR to keep checks green.

Note

🔒 Integrity filter blocked 2 items

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

• #19158 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [Cato Networks] Update changelog, version in manifest and Sync CODEOWNERS  #19158 pull_request_read: 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:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e4da4fe

History

• 💔 Build #43307 failed 322568d

[ShourieG]

We need to keep a forward upgrade path to versioning from next time, the current approach seems to break conventions.