[main] (forwardport #2635) Finalize changelog for 9.4 release

[mergify]

Finalize changelog for 9.4

---

This is an automatic backport of pull request #2635 done by Mergify.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[github-actions]

ECS PR Triage (automated)

PR Triage Report

PR: #2639 — [main] (forwardport #2635) Finalize changelog for 9.4 release
Classification: Direct PR
Change type: Documentation
Scope: Minor

Summary

This is an automated Mergify forwardport of PR #2635. It finalizes the changelog for the ECS 9.4.0 release by moving entries from CHANGELOG.next.md into CHANGELOG.md. This is standard release-process housekeeping — changelog rotation — and requires no RFC or maintainer discussion per classification-rules §0 (release process PRs are always Direct PR).

Files changed

• Schemas: none
• Generated: none
• Tooling/scripts/tests: none
• Docs (hand-authored): none
• CI / GitHub: none
• RFCs: none
• Release / changelog: CHANGELOG.md (+15 lines), CHANGELOG.next.md (−14 lines)

Routing decision

Direct PR — This PR exclusively touches release mechanics: it moves the 9.4.0 section (Tooling and Artifact Changes — Added and Improvements) from CHANGELOG.next.md into the permanent CHANGELOG.md. Per classification-rules §0, release PRs that only perform changelog rotation, version bumps, or release-note shuffling are always Direct PR regardless of how many files change. No schema, tooling, or behavioral changes are introduced.

Risk notes

• Breaking / deprecation: No. The changelog entries being moved were already merged in prior PRs; this PR only relocates them.
• OTel / semconv: N/A — no field or schema changes.
• Scope / reuse: N/A — no fieldset, reuse, or categorization changes.

Completeness checklist

• PR description (all sections) — Missing. The PR body is auto-generated by Mergify and does not fill in the 7 template sections. This is expected and acceptable for automated forwardport/release PRs; the original PR Finalize changelog for 9.4 release #2635 contains the authoritative description.
• CHANGELOG.next.md — Not required. Release process PRs do not need a new changelog entry; this PR is the changelog rotation itself.
• make + committed generated outputs — Not required. No schema changes.
• OTel otel: on new/changed semconv-related fields — N/A. No field changes.
• Tests / make check — N/A. No schema or tooling changes to validate.
• CLA (contributor) — N/A. Author is the Mergify bot performing an automated forwardport.

Recommended next actions

1. Maintainer: Verify that the 9.4.0 entries in CHANGELOG.md match the intended release content and that CHANGELOG.next.md retains the correct future-release scaffolding.
2. Maintainer: Approve and merge — this is low-risk, mechanical changelog rotation with no functional changes.

---

Posted by PR Triage workflow