[main](backport #52086) Add Beats 8.19.19 release notes

[mergify]

Adds Beats 8.19.19 release notes.

Checklist

• @pierrehilbert review this PR to make sure the correct items are included
• @elastic/ingest-docs review the language
• @elastic/ingest-docs copy generated content to the CHANGELOG.asciidoc file
• @pierrehilbert merge on release day

  ---

  This is an automatic backport of pull request Add Beats 8.19.19 release notes #52086 done by Mergify.

[mergify]

Cherry-pick of 6cc8e32 has failed:

On branch mergify/bp/main/pr-52086
Your branch is up to date with 'origin/main'.

You are currently cherry-picking commit 6cc8e32d9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/8.19.19.asciidoc
	new file:   changelog/8.19.19.yaml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   CHANGELOG.asciidoc
	deleted by them: changelog/fragments/1769821387-iis-add-cpu-number-information.yaml
	deleted by them: changelog/fragments/1770723983-osquerybeat-rrule-scheduling.yaml
	deleted by them: changelog/fragments/1773436535-libbeat-manager-shutdown-wait.yaml
	deleted by them: changelog/fragments/1774610344-1774610344-ldap-sspi-cbt.yaml
	deleted by them: changelog/fragments/1778707911-entityanalytics-okta-minimal-state.yaml
	deleted by them: changelog/fragments/1779435486-mborden-filebeat-auditd-parser.yaml
	deleted by them: changelog/fragments/1781553432-filestream-linereader-buffer-pool.yaml
	deleted by them: changelog/fragments/1781712219-honor-enabled-flag-in-filebeat.config.inputs.yaml
	deleted by them: changelog/fragments/1782385200-winlog-input-ga.yaml
	deleted by them: changelog/fragments/1783335960-osquerybeat-pack-name-query-name.yaml
	both modified:   libbeat/docs/release.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[github-actions]

TL;DR

All six failed Buildkite jobs have the same deterministic failure: pre-commit stops at check-merge-conflict because PR #52154 contains unresolved Git conflict markers in two tracked documentation files. This is a merge-resolution issue, not an infrastructure or flaky-test failure.

Remediation

• Resolve the conflicts and remove every <<<<<<<, =======, and >>>>>>> marker from CHANGELOG.asciidoc and libbeat/docs/release.asciidoc; preserve the intended 8.19.19 release notes and the existing main-branch content.
• Complete the cherry-pick/backport resolution, then run pre-commit run --all-files (or rerun the Buildkite pipeline) to confirm the merge-conflict hook passes.

Investigation details

Root Cause

The Buildkite logs for Filebeat, Packetbeat, Winlogbeat, x-pack/Packetbeat, x-pack/Winlogbeat, and x-pack/dockerlogbeat all fail at the same hook. The reported markers are:

• CHANGELOG.asciidoc:6, :7, and :437
• libbeat/docs/release.asciidoc:11, :17, and :25

The PR diff itself adds these conflict markers, and the PR is already labeled conflicts/blocked. The existing Mergify comment also records the failed cherry-pick with both files listed as unmerged.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/50019
• Jobs: https://buildkite.com/elastic/filebeat/builds/34837, https://buildkite.com/elastic/beats-packetbeat/builds/32120, https://buildkite.com/elastic/beats-winlogbeat/builds/31401, https://buildkite.com/elastic/beats-xpack-packetbeat/builds/31614, https://buildkite.com/elastic/beats-xpack-winlogbeat/builds/30914, https://buildkite.com/elastic/beats-xpack-dockerlogbeat/builds/29658
• Key log excerpt: check for merge conflicts ... Failed followed by Merge conflict string '<<<<<<<' found and corresponding =======/>>>>>>> markers in both files.

Verification

• Not run locally; diagnosis is directly confirmed by all six provided Buildkite logs and the PR diff.

---

What is this? | From workflow: PR Buildkite Detective

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