Repository navigation
Write the v1.4.1 changelog and update the README release wording. - #25
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
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.
CHANGELOG.md gets the full v1.4.1 section: module and toolchain, fixes, additions and project changes, one entry per change with the fork PR, the upstream PR and author, and the issues closed; every documented behaviour change is marked as changed.
The README no longer calls v1.4.1 a strict superset. It says what the release is: every exported identifier of v1.4.0 kept and checked by apidiff,
Tx.NamedQueryContextadded, Go 1.24 required, and the three behaviour changes named; a 1.4.1 block joins Recent Changes and the install section states the Go floor.