Skip to content

[v0.21.x] kvdb: mark pgx/v5 as direct dependency - #11012

Merged
ziggie1984 merged 1 commit into
lightningnetwork:v0.21.x-branchfrom
ziggie1984:fix-v021-kvdb-tidy
Jul 31, 2026
Merged

[v0.21.x] kvdb: mark pgx/v5 as direct dependency#11012
ziggie1984 merged 1 commit into
lightningnetwork:v0.21.x-branchfrom
ziggie1984:fix-v021-kvdb-tidy

Conversation

@ziggie1984

Copy link
Copy Markdown
Collaborator

Description

Follow-up to #10977.

Commit e7f9a9220 backported the Postgres migration bulk support to
v0.21.x-branch and introduced direct imports of github.com/jackc/pgx/v5
and github.com/jackc/pgx/v5/stdlib.

On master, pgx/v5 was already a direct kvdb dependency, so the original
commit needed no go.mod change. On v0.21.x-branch, it was still listed as
indirect. As a result, go mod tidy rewrites kvdb/go.mod and
make tidy-module-check fails. This surfaced again in the static checks for
#11010.

Run go mod tidy in the kvdb module to classify pgx/v5 as a direct
dependency. This does not change the selected version or go.sum.

Testing

make tidy-module-check

Backport PR lightningnetwork#10977 added direct pgx/v5 imports in commit e7f9a92 without updating kvdb/go.mod. Regenerate the module metadata with go mod tidy.

@saubyk saubyk left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack

@ziggie1984
ziggie1984 merged commit 672a8b0 into lightningnetwork:v0.21.x-branch Jul 31, 2026
40 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants