chore(deps): sweep foundation v0.5.5, validator and lucide-react for STM-4 - #1053
Merged
Conversation
…-react to 1.38.0 Clears the STM-4 dependency sweep: the only remaining drift is json-schema-to-typescript v16, already open as Renovate PR #986.
krisarmstrong
enabled auto-merge
September 7, 2026 20:11
krisarmstrong
changed the title
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
1 participant
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.
Summary
STM-4 dependency sweep from the stem v1 plan of record.
github.com/MustardSeedNetworks/foundationv0.5.2 → v0.5.5 (shared licencecrypto + CSRF manager; keeps stem in step with the fleet).
github.com/go-playground/validator/v10v10.30.3 → v10.30.4 — the only otherdirect Go dependency behind latest.
lucide-react1.34.0 → 1.38.0 inui/.After the sweep the only remaining drift in either ecosystem is
json-schema-to-typescriptv16, which Renovate has already opened as #986, soit is deliberately left alone here.
npm outdated(notnpm view) is thesource of truth for npm:
ui/.npmrcsetsmin-release-age=7, so anythingpublished in the last week is not resolvable by policy.
Linked Issue
Related to #577
Type of Change
Risk
Low. No source changes; three version bumps.
foundationis the sharedlicence/CSRF module, so the whole backend suite (including
internal/licenseat 80 % and the API auth tests) was run under the normalmake testgate. Thelucide-reactminor was checked by a full UI typecheckand production build in addition to vitest, which is what would catch a
removed or renamed icon export.
One thing to flag rather than decide silently:
min-release-age=7is an npm-sideguard only — there is no equivalent embargo on the Go side, per
~/Developer/.claude/CLAUDE.md. Both Go bumps here are inside a 7-day window(
validatorv10.30.4 published 2026-09-03,foundationv0.5.5 2026-09-05).foundationis our own module so the supply-chain rationale does not apply toit;
validatoris third-party and four days old. It is in policy as written,but if the fleet wants the npm embargo mirrored for gomod, this is the PR that
shows why — say so and I will drop the validator bump (it was not part of the
STM-4 row; foundation and lucide-react were).
Testing Evidence
Acceptance command from the plan row:
Security and Release Checklist
govulncheck ./...clean (0 affecting vulnerabilities)//nolintorbiome-ignoreadded