[9.0](backport #9440) [docs] Add Markdown release notes #9990
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=80&v=4){kind=small}
* add config.changelog.yaml * add changelog yml files * check 9.1.2 output * check 9.1.1 output * check 9.1.0 output * update 9.1.0.yaml * check 9.0.5 output * check 9.0.4 output * check 9.0.3 output * check 9.0.2 output * check 9.0.1 output * check 9.0.0 output * clean up yaml files * remaining formatting fixes * add build out docs-builder content * fix build errors * add links to other pages * add 9.0.6 release notes * add 9.1.3 release notes (cherry picked from commit 86fd0df) # Conflicts: # changelog/9.0.1.yaml # changelog/9.0.2.yaml # changelog/9.0.3.yaml # changelog/9.0.6.yaml # docs/docset.yml # docs/release-notes/index.md # docs/release-notes/toc.yml
mergify
bot
added
the
conflicts
mergify
bot
requested review from
michalpristas and
straistaru
and removed request for
a team
mergify
bot
added
the
conflicts
|
Cherry-pick of 86fd0df 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 |
github-actions
bot
added
Team:Docs
|
Backporting to 9.0 to support our release notes process |
ebeahan
reviewed
Sep 16, 2025
🔍 Preview links for changed docs |
ebeahan
approved these changes
Sep 16, 2025
Merged
|
💚 Build Succeeded
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
What does this PR do?
Adds generated Markdown Elastic Agent release notes here instead in the docs-content repo.
Why is it important?
Currently the Elastic Agent 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 Fleet Server release notes. This is time consuming for the docs team and often leads to delays in publishing release notes.
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 elastic-agent output when generating the release notes using thecolleenmcginnis:markdownbranch ofelastic-agent-changelog-tool.Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
This approach to release notes would mean splitting the source files for Fleet Server and Elastic Agent release notes, but they would still live next to each other on the docs site.
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.
Related issues
Questions to ask yourself
cc @ebeahan @pierrehilbert @bmorelli25
This is an automatic backport of pull request #9440 done by Mergify.