Merged
Conversation
Update version to 0.4.0 and add release notes covering: - Breaking change: VerticalLayout/HorizontalLayout default to Auto() sizing - Rich content support for SelectionListNode - Platform-native console for Windows with event-driven input - Formalized diagnostic tracing system
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.
Summary
Prepare release 0.4.0 with the following user-facing changes:
Breaking Changes
New Features
Rich content support for SelectionListNode (Add rich content support and interactive decision points to SelectionListNode #96)
SelectionItemContentPlatform-native console for Windows (Platform-native console abstraction for event-driven input #90)
Diagnostic tracing system (Add formalized diagnostic tracing system #84)
Changes
RELEASE_NOTES.mdwith version 0.4.0Directory.Build.propswith new version and package release notesPost-Merge Actions
After this PR is merged, the release tag
0.4.0(no 'v' prefix) will be created and pushed to trigger the automated release workflow.