Repository navigation
Prepare v1.4.2: retract the upstream tags and write the changelog entry - #35
Merged
Merged
Conversation
…write the changelog entry.
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.2. No code change; the tag is not pushed until this is reviewed and merged.
go.mod
retract [v1.2.0, v1.4.0]with a rationale comment. Those versions are upstream's tags, pushed with the history; their go.mod declaresgithub.com/jmoiron/sqlx, sogo get github.com/secondwindoss/sqlx@v1.4.0fails with a module path error. Retractions are read from the latest version's go.mod, so this takes effect once v1.4.2 is tagged.CHANGELOG
v1.4.2 (2026-10-19): the nesteddbtestmodule (Move the database tests into a nested dbtest module so go.mod requires no other module #34), the retraction (this PR), and a Project section for signed tags, Scorecard, SHA-pinned actions, fuzz tests, CodeQL, the required CI check and the README rewrite (Say in the README that a replace directive cannot stand in for the import rewrite. #28 to Add the OpenSSF Scorecard badge to the README #33). If the tag is pushed on a later day, the date should change with it.README and bug template
@v1.4.2from the merge on, so the tag should follow the merge directly.Verified locally with a file-based GOPROXY serving the real v1.2.0 to v1.4.1 files plus this branch as v1.4.2:
go list -m -versionslistsv1.4.1 v1.4.2; with-retractedall ten;@latestis v1.4.2; v1.4.0 reports the rationale; a module on v1.4.1 sees[v1.4.2]ingo list -m -u.go list -m allshows only sqlx (on v1.4.1 the three drivers and edwards25519 came along).After merge:
git tag -s v1.4.2 -m "v1.4.2"on the merge commit, push the tag, create the GitHub release from the changelog entry, warm the proxy, then repeat the checks above against proxy.golang.org.