[9.1](backport #5374) [docs] Add Markdown release notes #5521
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
* copy over changelog yaml files * render release notes, make them publishable (cherry picked from commit b73980b) # Conflicts: # docs/docset.yml # docs/release-notes/index.md # docs/release-notes/toc.yml
mergify
bot
added
the
conflicts
|
Cherry-pick of b73980b has failed: 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 |
mergify
bot
added
the
conflicts
🎉 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) |
github-actions
bot
added
documentation
|
|
Backporting to 9.1 to support our release notes process |
ebeahan
approved these changes
Sep 16, 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.
🍷 Pairs with elastic/elastic-agent-changelog-tool#213 elastic/elastic-agent#9440
What is the problem this PR solves?
Currently the Elastic Agent Control Plane team generates release notes in AsciiDoc in this repo and the @elastic/ingest-docs team has to manually translate AsciiDoc to Markdown, copy to another repo (docs-content), split into multiple files, and integrate with Elastic Agent release notes. This is time consuming for the docs team and often leads to delays in publishing release notes.
How does this PR solve the problem?
In elastic/elastic-agent-changelog-tool#213, I updated the automation to allow generating Markdown, formatting it, and putting it into the correct files directly using
elastic-agent-changelog-tool. This is the fleet-server output when generating the release notes using thecolleenmcginnis:markdownbranch ofelastic-agent-changelog-tool.This PR adds generated Markdown Fleet Server release notes here instead in the docs-content repo.
How to test this PR locally
This repo is not currently hooked up to the docs build system so we don't have a PR preview yet, but you can build the docs locally.
Note: Right now it will build independently from the rest of the Release notes, but once this repo is hooked up to the docs build system, these release notes will be integrated into the larger Release notes table of contents.
Design Checklist
This is a docs-only change.
Checklist
This is a docs-only change.
Related issues
cc @ebeahan @pierrehilbert @bmorelli25
This is an automatic backport of pull request #5374 done by Mergify.