Add the release notes of 0.1.0 with its known issues - #6
Merged
Merged
Conversation
The GitHub release of a version now says what release_notes/<version>.md says when there is one, before the tag message and the generated notes. The notes of 0.1.0 list the known Tcl/Tk issues: standalone Python builds on Linux, fixed by VUnit#3, and the Tcl version clash on Windows, VUnit#5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… notes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds
release_notes/0.1.0.md, the notes of the 0.1.0 release, with the known issues:publish.ymlused the tag message, or else generated notes, for the GitHub release. It now usesrelease_notes/<version>.mdfirst when there is one, so the notes are reviewed like any other change before the tag is pushed. The other two stay as fallbacks.If #3 is merged before 0.1.0 is tagged, the first known issue should go.
🤖 Generated with Claude Code