Repository navigation
v0.7.3 chore(deps): bump all dependencies to latest stable - #12
Merged
Merged
Conversation
Dependency-only release. No source file changed and no public API moved. Direct dependencies: go-errs v1.0.3 to v1.0.4, go-sqldb and go-sqldb/pqconn v1.3.0 to v1.4.0, golog v1.1.1 to v1.2.1, go-types to the latest commit, and testify v1.11.1 to v1.12.1. Indirect requirements followed from those. Two consumer-visible effects come from upstream rather than from this repo. go-errs v1.0.4 gives wrapped errors a StackTrace() []uintptr method in the pkg/errors shape, and golog v1.2.0 makes logsentry surface a logged Err as a Sentry exception carrying that stack trace, with the error text as the issue subtitle instead of "(No error message)". A consumer running the Sentry log writer sees job failure issues change shape without changing anything on their side. go-sqldb v1.4.0 reworked ScanDriverValue to mirror the database/sql conversions, making scanning more permissive than before, not less. Two modules cannot be pinned to a stable version because upstream has published none. go-types has no semver tags at all, so it stays a pseudo-version. go.yaml.in/yaml/v4, pulled in through go-types and testify, has only release candidates; it is held at v4.0.0-rc.4, the lowest release our own dependencies require, rather than advanced to the newest rc for no reason. tools/go.mod moved revive v1.15.0 to v1.16.0 and gosec v2.27.1 to v2.29.0. Neither reports a new finding on this codebase. That module is tidied from inside tools/ with go mod tidy -C tools; running tidy from the repo root with -modfile=tools/go.mod pulls the root module's own packages into it. Also adds the v0.7.2 compare link the previous release left out of the CHANGELOG link list.
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.
Dependency-only release. No source file changed and no public API moved.
Direct dependencies
github.com/domonda/go-errsgithub.com/domonda/go-sqldbgithub.com/domonda/go-sqldb/pqconngithub.com/domonda/gologgithub.com/stretchr/testifygo-typesmoved tov0.0.0-20260902160716-5c6c50f32fcd. Indirect requirementsfollowed from those.
What a consumer actually notices
Job errors reported through Sentry get better, and neither change is in this
repo.
go-errsv1.0.4 gives wrapped errors aStackTrace() []uintptrmethod inthe
pkg/errorsshape, andgologv1.2.0 makeslogsentrysurface a loggedErras a Sentry exception carrying that stack trace, with the error text asthe issue subtitle instead of "(No error message)". Anyone running the Sentry
log writer sees job failure issues change shape without changing anything on
their side.
go-sqldbv1.4.0 reworkedScanDriverValueto mirror thedatabase/sqlconversions, so scanning is more permissive than before, not less.
Two things that could not be pinned to a stable version
Upstream has published none:
go-typeshas no semver tags at all (go list -m -versionsreturns nothing),so a pseudo-version is the only option.
go.yaml.in/yaml/v4(indirect, viago-typesandtestify) has onlyv4.0.0-rc.1throughrc.6. Held at rc.4, the lowest release our owndependencies require, rather than advanced to the newest rc for no reason.
Tooling
tools/go.mod:revivev1.15.0 to v1.16.0,gosecv2.27.1 to v2.29.0. Neitherreports a new finding on this codebase.
Note for whoever touches that module next: tidy it from inside
tools/(go mod tidy -C tools). Running tidy from the repo root with-modfile=tools/go.modpulls the root module's own packages into it.
Verification
./scripts/run-tests.shon the final tree:go vet,revive,gosec, then allfour packages against a temp PostgreSQL database.
Also adds the v0.7.2 compare link the previous release left out of the CHANGELOG
link list.