changelog: security_detection_engine 8.19.33 (backport sync from PR #21301)

[github-actions]

Automated changelog sync from backport PR #21301.

Generated by the sync-backport-changelog workflow.

[github-actions]

TL;DR

The failing Buildkite job is an external OOM FTR test failure (expected 200, got 502 Bad Gateway) and does not map to code changed in this PR. Immediate action is to rerun the failed OOM test job; if it reproduces consistently, investigate Kibana/FTR environment health for that pipeline.

Remediation

• Retry the failed Buildkite OOM test step for this PR/build.
• If it fails again, inspect the downstream FTR environment/service behind the prebuilt-rules install API in the appex-qa-stateful-security-prebuilt-rules-ftr-oom-testing pipeline.
• Confirm this PR still only changes packages/security_detection_engine/changelog.yml before re-running required checks.

Investigation details

Root Cause

The only failed job is Run FTR OOM tests in a downstream pipeline, and the failure is an HTTP gateway error in Kibana API integration tests, not a compile/test assertion tied to this repo diff.

• Failing assertion points to Kibana test code path outside this repository:
  x-pack/solutions/security/test/security_solution_api_integration/test_suites/detections_response/rules_management/prebuilt_rules/oom_testing/install_prebuilt_rules/install_prebuilt_rules.ts:133
• PR diff contains only changelog metadata edits in packages/security_detection_engine/changelog.yml (hunk @@ -470,6 +470,11 @@) and no runtime code/test logic changes.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/49809
• Failed job: Run FTR OOM tests (package version: 9.5.5, EPR: ...epr-oom.estc.dev)
• Key log excerpt:

Error: expected 200 "OK", got 502 "Bad Gateway"
at Context.<anonymous> (x-pack/.../install_prebuilt_rules.ts:133:10)

Verification

• Not run locally (failure is in external Buildkite FTR environment and references Kibana test harness paths unavailable in this checkout).

Follow-up

If retries show a stable repro, capture the response body/server logs for the failing 502 endpoint in the OOM FTR environment to determine whether it is service readiness/resource pressure versus a behavioral regression.

---

What is this? | From workflow: PR Buildkite Detective

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

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: d5e8c00

History

• 💔 Build #49809 failed f93766e

cc @shashank-elastic