Repository navigation
fix(deps): resolve security advisories + add dependabot config - #12
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 216 216
=========================================
Hits 216 216 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Resolves the 17 open Dependabot security alerts on this repo and adds
.github/dependabot.ymlso future advisories raise update PRs automatically instead of silently accumulating.Dependency bumps
golang.org/x/cryptogithub.com/moby/sys/usergithub.com/opencontainers/runcThe
x/cryptocriticals are all in the SSH subsystem (golang.org/x/crypto/ssh). pgxschema is a Postgres schema-migration library with no SSH usage, so there's no reachable exploitation path in this codebase — bumping clears the alerts regardless.runcwas pinned to v1.3.6 (the minimal version satisfying the advisory's>1.3.5fix) rather than the current latest (v1.5.2), because v1.5.2 removed thelibcontainer/userpackage thatory/dockertest'sdocker/pkg/homedir(a test-only transitive dependency) still imports, which breaksgo mod tidy. v1.3.6 keeps the package and is already past the vulnerable threshold.Not bumped — no fix exists in this major version
github.com/jackc/pgx/v4(GHSA-j88v-2chj-qfwx, SQL injection via placeholder confusion): the GitLab advisory for the v4 module states "there is no solution available" — the fix landed only inpgxv5.9.2+. v4 is EOL/archived; v4.18.3 (already pinned) is the latest release on that line. Migrating to v5 is an API-breaking change out of scope for this dependency-bump PR.github.com/jackc/pgproto3/v2(GHSA-jqcq-xjh3-6g23, DoS via negative field length panic): same situation — this is an archived dependency of pgx v4; the fix exists only in pgx v5's internal (non-modularized) pgproto3. v2.3.3 (already pinned) is the latest release of the standalone/v2module.Both would require a pgx v4→v5 migration to resolve, which changes pgxschema's public API surface. Flagging for a separate, deliberate migration decision rather than forcing here.
New:
.github/dependabot.ymlWeekly
gomod+github-actionsupdate checks, so version-update PRs are raised automatically going forward instead of alerts silently piling up with no action.Verification
go build ./...— passgo vet ./...— passgo test ./...— pass (14.2s; dockertest provisions its own Postgres container, no external DB needed)