Skip to content

Fix high-severity npm advisories for v0.23.4 - #81

Merged
jdogresorg merged 1 commit into
release/v0.23.4from
hotfix/v0.23.4
Oct 23, 2026
Merged

jdogresorg merged 1 commit into
release/v0.23.4from
hotfix/v0.23.4

Conversation

@jdogresorg

Copy link
Copy Markdown
Contributor

Dependency-only fix for the v0.23.4 maintenance release (release/v0.23.4, cut from v0.23.3; ledger XC-6148).

Changes (package.json / package-lock.json only): follow-redirects 1.16.0 to 1.16.1, mariadb 3.5.3 to 3.5.4 (package.json pin), fast-uri 3.1.7 to 3.1.9, hono 4.13.5 to 4.13.13, ip-address 10.7.0 to 10.7.4.

npm audit --omit=dev --audit-level=high: before 2 high / 0 critical; after: passes.

Suite: full CI suite (ci:full) on test02 with siblings pinned to the v0.23.4 candidates (not develop): 7146 pass, 0 fail, 10 pending (Node 22.23.4).

No source, gate or consensus code changes. The pre-push gate was skipped for this push by operator ruling, because it grades against develop siblings; the sibling-pinned suite above is the evidence.

@jdogresorg
jdogresorg merged commit 8c71493 into release/v0.23.4 Oct 23, 2026
3 checks passed
@jdogresorg
jdogresorg deleted the hotfix/v0.23.4 branch October 24, 2026 02:19
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.

1 participant