sqldb: register migration 14 in migration config
What the developer wrote
Authored by ziggie
sqldb: register migration 14 in migration config
Add the 000014_payments_no_fail_reason_index migration to the
main migration configuration so the global migration list stays in
sync with the embedded SQL schema files.
What changed, and why it matters
This commit is a small bookkeeping fix: it adds a previously-created database migration to the master list so that LND's database upgrade tracker knows about it. On its own, the change does not introduce a security vulnerability or fix an exploitable bug. However, if the migration had been left unregistered, future upgrades could potentially get out of sync, which in database systems can sometimes lead to inconsistent state or upgrade failures.
No immediate security action required. Treat as a normal code/maintenance review. Verify that the registered Version and SchemaVersion match the embedded SQL file and that no other migrations are missing from the list.
Security signals we found
Database migration registration only
No change to SQL schema content or application logic
No authentication, authorization, or cryptographic changes
Potential operational risk if migrations drift from schema state
Evidence from the diff
The patch registers migration ‘000014_payments_no_fail_reason_index’ (Version 17, SchemaVersion 14) in sqldb/migrations.go. The SQL file itself already existed; this change only adds the metadata entry that tells the migration framework to apply it. There is no code logic change, no cryptographic change, and no direct security boundary change in the diff.
Changed components
sqldb/migrations.goLND database migration frameworkInspect captured patch +5 / −0
diff --git a/sqldb/migrations.go b/sqldb/migrations.go
index c2a3ac2..9f9256d 100644
--- a/sqldb/migrations.go
+++ b/sqldb/migrations.go
@@ -126,6 +126,11 @@ var (
Version: 16,
SchemaVersion: 13,
},
+ {
+ Name: "000014_payments_no_fail_reason_index",
+ Version: 17,
+ SchemaVersion: 14,
+ },
}, migrationAdditions...)
// ErrMigrationMismatch is returned when a migrated record does not
Why this scored 22/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.