[9.2](backport #5565) [docs] Refine Markdown release notes structure #5606
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit a02bf19)
github-actions
bot
added
documentation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
colleenmcginnis
approved these changes
Oct 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
These updates will (1) eliminate any manual steps in the resulting fleet-server release notes PR outside of copy edits, and (2) reduce the chance of conflicts when forward porting to later minors and main (like we ran into in in elastic-agent in elastic/elastic-agent#10032 and elastic/elastic-agent#10031).
How does this PR solve the problem?
Reorganizes the
release-notes/_snippetsfile structure to be compatible with elastic/elastic-agent-changelog-tool#220.How to test this PR locally
There will be a docs preview.
Related issues
elastic/elastic-agent-changelog-tool#220
cc @karenzone
This is an automatic backport of pull request #5565 done by Mergify.