Update Elasticsearch release notes automation #132930
Merged
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
charlotte-hoblik
requested review from
brianseeders,
leemthompo and
szabosteve
charlotte-hoblik
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
|
@charlotte-hoblik If we go down the road of only publishing the release notes on release day, I think we can probably avoid using
This would just require @brianseeders adjusting the RNs tool to no longer require a follow up PR to remove the coming tags. :) |
|
Good point @leemthompo I was actually debating this idea myself. I’ll just remove that part from the changes. |
charlotte-hoblik
changed the title
leemthompo
approved these changes
Aug 14, 2025
* [docs] Add support for overriding entries in the release notes * Update changelog bundles with overrides
|
Pinging @elastic/core-docs (Team:Docs) |
|
I ended up updating the tag from |
charlotte-hoblik
changed the title
JeremyDahlgren
pushed a commit
to JeremyDahlgren/elasticsearch
that referenced
this pull request
Aug 29, 2025
* Update breaking changes and deprecations * update release note tagging * revert tagging change * Update tests after template changes * [docs] Add support for overriding entries in the release notes (elastic#133592) * [docs] Add support for overriding entries in the release notes * Update changelog bundles with overrides * Use ga instead of comming tag * Update tests after template change --------- Co-authored-by: Brian Seeders <[email protected]>
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.
This PR adds editorial changes to match release notes guidance
Updates the automated “no changes” messages to follow the latest style guidance:
No breaking changes in this version→There are no breaking changes associated with this release.No deprecations in this version→There are no deprecations associated with this release.Updating the “no changes” messages improves clarity and ensures consistency across products.
comingtag togaConnected to
https://github.com/elastic/developer-docs-team/issues/334