Skip to content

[wip] Update release notes automation to use new markdown format #124161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 38 commits into
base: main
Choose a base branch
from

Conversation

brianseeders
Copy link
Contributor

No description provided.

@leemthompo
Copy link
Contributor

leemthompo commented Mar 25, 2025

FYI this PR to update headings might be relevant to your templates: #125548

@@ -20,318 +21,609 @@ To check for security updates, go to [Security announcements for the Elastic sta
% ### Fixes [elasticsearch-next-fixes]
% *

## 9.1.0 [elasticsearch-910-release-notes]
## 9.0.1 [elasticsearch-901-release-notes]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@brianseeders remember per elastic/docs-content#1152 we need these to be in X.Y.Z format going forward so these IDs should be 9.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants