Tag new releases for kvdb, queue, and sqldb submodules to drop root replace directives

[ziggie1984]

The root go.mod carries three replace directives that point submodules at the in-tree copy:

// TODO(gijs): remove once new queue package is released.
replace github.com/lightningnetwork/lnd/queue => ./queue

// TODO(elle): remove once the gossip V2 sqldb changes have been made.
replace github.com/lightningnetwork/lnd/sqldb => ./sqldb

// TODO: remove once kvdb with pgx/v5 is released.
replace github.com/lightningnetwork/lnd/kvdb => ./kvdb

The awaited changes already exist on master but no tag has been cut that contains them:

• queue — last tag queue/v1.1.1. Master contains queue: add BackpressureQueue[T] with Random Early Drop (ea8a665), which is the "new queue package" referenced in the TODO. Needs queue/v1.2.0.
• kvdb — last tag kvdb/v1.4.16. Master contains kvdb: bump pgx/v4/stdlib to pgx/v5/stdlib (848af80) — the pgx/v5 change called out in the TODO. Needs kvdb/v1.5.0.
• sqldb — last tag sqldb/v1.0.12 (root go.mod still pins v1.0.11). Master contains the full sqldb/v2 work and the gossip-V2-related schema/queries. Needs the next sqldb release once the v2/gossip work is ready to ship.

Action items

• Cut kvdb/v1.5.0 containing the pgx/v5 migration.
• Cut queue/v1.2.0 containing BackpressureQueue[T].
• Cut the next sqldb tag once gossip-V2 changes have landed (separate scope; track here so we don't forget).
• Bump root go.mod require versions and remove the three replace directives.
• Run go mod tidy and make tidy-module-check.

Related

• Root go.mod lines 200–207

[ziggie1984]

I checked the in-tree module graph as of May 28, 2026. This issue should also cover updating the nested go.mod files, not only the root module, because several released lnd submodule tags are not being consumed by downstream submodules yet.

Current latest tags observed on origin:

• fn/v2.0.9
• healthcheck/v1.2.6
• kvdb/v1.5.1
• queue/v1.2.0
• sqldb/v1.0.13
• ticker/v1.1.1
• tor/v1.1.6

Outdated in-tree requirements I found:

File	Current	Should check/bump to
root go.mod	kvdb v1.5.0	kvdb v1.5.1
root go.mod	sqldb v1.0.11 plus local replace	sqldb v1.0.13 if it contains the needed gossip-v2 changes, then remove replace
kvdb/go.mod	healthcheck v1.2.4	healthcheck v1.2.6
kvdb/go.mod	sqldb v1.0.6	sqldb v1.0.13 if compatible
kvdb/go.mod	indirect ticker v1.1.0	ticker v1.1.1
kvdb/go.mod	indirect tor v1.0.0	tor v1.1.6
actor/go.mod	fn/v2 v2.0.8	fn/v2.0.9
actor/go.mod	queue v1.1.1 plus local replace	queue v1.2.0, then remove replace
actor/go.mod	indirect ticker v1.0.0 plus local replace	ticker v1.1.1, then remove replace
queue/go.mod	fn/v2 v2.0.8 plus local replace	fn/v2.0.9, then remove replace
queue/go.mod	ticker v1.0.0 plus local replace	ticker v1.1.1, then remove replace
healthcheck/go.mod	ticker v1.1.0	ticker v1.1.1
healthcheck/go.mod	tor v1.0.0	tor v1.1.6
sqldb/v2/go.mod	fn/v2 v2.0.8	fn/v2.0.9
tlv/go.mod	fn/v2 v2.0.2	fn/v2.0.9

Suggested extra checklist item for this issue:

• Audit every in-tree module go.mod for github.com/lightningnetwork/lnd/* requirements, bump them to the latest released compatible tags, remove local replaces where the released tags now make them unnecessary, then run module tidying/checks for the affected modules.

[ziggie1984]

Follow-up: I checked every go.mod in the repo, not just the root module.

Covered modules:

• root go.mod
• actor
• cert
• clock
• fn/v2
• healthcheck
• kvdb
• queue
• sqldb
• sqldb/v2
• ticker
• tlv
• tor
• tools
• tools/linters

For this specific lnd-internal tag audit, cert, clock, fn/v2, sqldb, ticker, tor, tools, and tools/linters do not currently require any older github.com/lightningnetwork/lnd/* module tags. sqldb/v2 has no release tag on origin yet; it currently imports fn/v2 v2.0.8, so it should also be included in the bump to fn/v2.0.9.

The remaining outdated lnd-internal requirements/replaces are the rows listed above: root, actor, healthcheck, kvdb, queue, sqldb/v2, and tlv.