Repository navigation
Prepare the next release notes - #13
Draft
github-actions[bot] wants to merge 3 commits into
Draft
github-actions[bot] wants to merge 3 commits into
github-actions[bot] wants to merge 3 commits into
Conversation
Release-Notes-Base: 81c487f
This branch has not been deployed
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
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.
Collect pending release notes into
CHANGELOG.md.This draft is refreshed from
mainafter merges. Each update collects the Markdownfragments and removes the collected files in this branch. Released history is preserved.
No issue is required for a fragment; link the implementation PR or issue in its text
when useful. Edit fragments in implementation PRs rather than this generated draft.
To prepare the release, mark this PR ready to freeze automatic updates, then follow
docs/developer_guide/releasing.md.Review the notes, choose the version and date, and update the version records here.
Tagging and publishing remain manual. Required checks still apply; approve any pending
workflow runs before merging. Nothing in this workflow approves or merges a PR.