Repository navigation
Prepare v1.4.3: changelog entry and install lines - #37
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.
Release prep for v1.4.3, a patch release for the batch insert fix in #36. No code change; the tag is not pushed until this is reviewed and merged.
CHANGELOG
v1.4.3 (2026-10-19)with a one-paragraph summary; both fix entries now cite Return an error for a batch insert whose VALUES group never closes #36. If the tag is pushed on a later day, the date should change with it.README and bug template
retract [v1.2.0, v1.4.0]line stays in go.mod, because Go reads retractions from the latest version's go.mod.After merge:
git tag -s v1.4.3 -m "v1.4.3"on the merge commit once master CI is green, push the tag, create the GitHub release from the changelog entry, warm the proxy, then check@latest,go list -m -versions(v1.4.1 v1.4.2 v1.4.3) and that the retraction still applies.