Repository navigation
chore: update all dependencies - #30
Merged
Merged
Conversation
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
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
Updates every dependency to its latest version — npm devDependencies, the pinned package manager, and the toolchain transitives. GitHub Actions refs and the pandoc pin were verified against the latest releases and require no changes.
npm devDependencies
Toolchain
packageManager; also used locally to regenerate the lockfile). Lockfile format unchanged. Transitive refresh (re-resolved at PR-latest): biome 2.5.14, oxlint 1.83.0 (tsgolint 7.0.2002), jscpd 5.3.0, undici-types 8.9.0, vite 8.2.2 → 8.3.0, rolldown 1.2.9, magic-string 1.4.1, and the now-unreferencedtsx/esbuildtrees dropped entirely (leftovers from ts-canon < 0.2.0's tsx dependency).actions/checkout@v7.0.1,actions/setup-node@v7.0.0,pnpm/action-setup@v6.1.0are all current.pnpm/action-setuppicks up pnpm 12.5.1 automatically from thepackageManagerfield.ts-canon 0.2.0
Notable upstream changes: the CLI now runs on Node native type stripping (drops the
tsxdependency), relative lint/format paths are honored, and a newno-unsafe-castast-grep rule applies — the template sources pass it cleanly.minimumReleaseAgeExclude — resolved
ts-canon 0.2.0 was published 2026-09-20 19:00 UTC, inside pnpm 12's default 24-hour
minimumReleaseAgesupply-chain window, so this PR initially carried aminimumReleaseAgeExclude: [ts-canon@0.2.0]entry inpnpm-workspace.yaml(12e5bbc's parent). ts-canon 0.2.0 is now past the 24-hour window and the exclusion has been removed (12e5bbc) —pnpm-workspace.yamlis byte-identical tomain, and the lockfile passes the policy check with defaults only.Verification
All from a clean
node_moduleswith pnpm 12.5.1:pnpm install --frozen-lockfile— passes (exit 0), including the supply-chain policy check with no exclusionspnpm build(tsc) — cleanpnpm lint— exit 0: biome, oxlint (0 warnings / 0 errors), all ast-grep rules (incl. newno-unsafe-cast), pandoc check (2 files byte-identical), peer-deps, audit (no known vulnerabilities), jscpd (0 clones)pnpm test— 3/3 tests passed, 100% coverage