Repository navigation
Release v2.3.1 - #31
Merged
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
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.
Prepare v2.3.1 for the merged Briefing presentation, Markdown preview, comparison-menu, and dry-run plan fixes. Bump the package version and bring the release roadmap up to date, including the preceding v2.2.4 and v2.3.0 entries.
The release tag will be created from the merged commit after CI passes. The existing release workflow builds all six platform archives, publishes both installers and checksums, and verifies the published installers on Linux, macOS, and Windows.
Validation: source CLI reports 2.3.1; release-workflow checks and whitespace validation pass. Full CI runs on this PR before tagging.