2.3.0 - #14
Merged
Merged
2.3.0#14
Conversation
Merge only after v2.3.0-beta.1 is approved and verify-published is green for it.
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
1 participant
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.
Sets the version to 2.3.0 and dates its changelog section (2026-09-28; adjust the date if the release day differs, release.yml checks that the heading is dated). No other change: 2.3.0 is the same code as 2.3.0-beta.1.
Merge only after the v2.3.0-beta.1 release run (36375599177) is approved and
verify-publishedis green for 2.3.0-beta.1. After the merge and a greencion master, the tagv2.3.0starts release.yml, which waits for the approval again.Checked locally: build, 103 tests on net10.0, pack, consumers of the packed 2.3.0 on net10.0 and net48, the release notes extraction and the dated-heading check for 2.3.0.