chore(deps): update dependencies to latest patch/minor versions - #39
Merged
Conversation
Updates all out-of-range patch/minor dependencies via 'pnpm up' while staying within current major versions (typescript, pinia, jsdom, markdown-it, oui-data left on their current majors). Regenerates pnpm-lock.yaml, resolving the CI supply-chain 'minimumReleaseAge' failure (@types/node 26.1.2 had been committed within pnpm 11's 1-day release-age window; now resolves 26.3.0). Bumps .nvmrc 18.18.2 -> 24 to match CI, since the updated toolchain (vite 8, eslint 10, jsdom 29, pnpm 11.9) requires Node >= 20.19. Note: crypto-js@4.2.0 (deprecated/unmaintained) is intentionally left as-is; replacement is a separate decision.
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.
Description
Updates all out-of-range patch/minor dependencies to their latest versions
while staying within current major versions. No breaking changes.
This also fixes the CI failure on
main, wherepnpm iwas failing withERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION:@types/node@26.1.2had been committedwithin pnpm 11's 1-day release-age supply-chain window. Regenerating
pnpm-lock.yamlnow resolves@types/node@26.3.0, which passes the policy(
✓ Lockfile passes supply-chain policies).Included
naive-ui, @vueuse/*, @tabler/icons-vue, marked, figlet, dompurify, uuid,
libphonenumber-js, js-base64, etc.)
pnpm-lock.yamlregenerated (fixes the supply-chain check).nvmrc18.18.2→24to match CI (toolchain now requires Node ≥ 20.19)auto-imports.d.ts/.eslintrc-auto-import.jsonupdated consistentlyDeliberately excluded (separate follow-ups)
7.0.2, pinia4.0.3, jsdom30, markdown-it15,oui-data
2— breaking changes, need individual validation.crypto-js@4.2.0(deprecated/unmaintained) left as-is. Replacement is aproduct decision: hashing/HMAC could move to
@noble/hashes, but the encryptiontool's legacy ciphers (RC4/Rabbit/TripleDES) have no maintained audited
equivalent, and swapping AES would break decrypting existing ciphertext.
Validation
pnpm lint— 0 errors (2 pre-existing warnings)pnpm test— 33 files / 138 tests passedpnpm typecheck— passedpnpm build— passedpnpm i— supply-chain policy check passesAdditional context
Reviewed via adversarial review — PASS-WITH-CAVEATS, no blockers. The two
caveats (stale
.nvmrc, now fixed here;crypto-jsdeprecation, noted above)are both captured.