chore(deps): major updates -- typescript 7, better-sqlite3 13 - #157
Conversation
The non-security majors renovate grouped in #130 and dependabot split across #132/#133, resolved with `npm install --before=2026-09-08` so each release clears the 7-day minimumReleaseAge gate: - typescript 6.0.3 -> 7.0.2 (the native compiler; `tsc`, `tsc --noEmit` and `tsc -p tsconfig.scripts.json` all pass unchanged under strict mode) - better-sqlite3 12.10.0 -> 13.0.3 (N-API build; SQLite 3.53.4; in-process smoke opens an in-memory DB and queries it) - @types/better-sqlite3 7.6.13 -> 9.6.0 (tracks the runtime major) Left out on purpose: @vitest/coverage-v8 5.x from #130 -- it requires vitest 5, and vitest stays on 4.1.x; puppeteer 25 and @fastify/rate-limit 11 already landed with the security fixes. Verified: typecheck, typecheck:scripts, build, check:node-pin, test:coverage (1670 passed / 11 skipped), audit 0 vulnerabilities. Supersedes #130, #132, #133. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
This was written agentically; verify its assertions: Adversarial review receipt
🤖 Co-authored by Claude Fable 5.1. |
|
This was written agentically; verify its assertions: Review ledgerMachine-readable record of every review already performed on this PR. {
"version": 1,
"pr": 157,
"repo": "wrzonance/DMXr",
"reviews": [
{
"kind": "adversarial",
"provider": "codex",
"model": "gpt-5.6-sol",
"effort": "xhigh",
"mode": "cross-provider",
"harness": "claude",
"head_sha": "c5880f60ef007b8783ede2719856e0a10dee5543",
"covered_heads": [
"353f3026ccc6c8dbffd921ae507e8f14bbe8bde6",
"57fd500c0d3761030cd43d22a9c90b006587e160",
"c5880f60ef007b8783ede2719856e0a10dee5543"
],
"counts": {
"p1": 0,
"p2": 0
},
"reviewed_at": "2026-09-15T17:31:05Z",
"coverage": [
{
"sha": "353f3026ccc6c8dbffd921ae507e8f14bbe8bde6",
"reason": "merge-down:fd3de2ebd44fa256fa272d3a79a1d994bd5e3e8c",
"covered_at": "2026-09-15T17:34:03Z"
},
{
"sha": "57fd500c0d3761030cd43d22a9c90b006587e160",
"reason": "fix:ci-retrigger-after-github-test-merge-race",
"covered_at": "2026-09-15T17:43:22Z"
}
]
}
]
}🤖 Co-authored by Claude Fable 5.1. |
GitHub generated two refs/pull/157/merge commits one second apart at the last push (4cf53fd at 17:33:19Z, ed2376e at 17:33:20Z; identical parents fd3de2e + 353f302). The CodeQL run captured the first while the PR's merge ref settled on the second, so the recorded analysis does not match the PR's merge_commit_sha and the pre-merge gate cannot prove code-scanning completion. A rerun reuses the original checkout SHA, so only a fresh push produces a run against the settled merge commit. No content change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was written agentically; verify its assertions:
Why
Renovate's grouped major PR (#130) bundled
@vitest/coverage-v85.x, which requires vitest 5 and would break the test job against vitest 4.1.x, and dependabot's per-package majors (#132, #133) conflict with the lockfile after #153 and #155. Landing the two majors that are actually safe, fresh onmain.What
tsc,tsc --noEmit, andtsc -p tsconfig.scripts.jsonpass unchanged under strict modeDeliberately left out:
@vitest/coverage-v85.x (needs vitest 5). Resolved withnpm install --before=2026-09-08so each release clears the 7-dayminimumReleaseAgegate. No source changes. Supersedes #130, #132, #133, which are closed as outdated.Testing
npm run typecheck,typecheck:scripts,build,check:node-pinpass on TypeScript 7.0.2select sqlite_version()→ 3.53.4)npm run test:coverage: 1670 passed, 11 skippednpm audit --audit-level=high: 0 vulnerabilitiesci:retrigger. GitHub generated tworefs/pull/157/mergecommits one second apart at the previous push; CodeQL scanned the first while the PR's merge ref settled on the second, so the pre-merge gate could not match the analysis to the PR's merge commit. A rerun reuses the original checkout SHA, so a fresh push was the only way to get a scan of the settled merge commit.🤖 Co-authored by Claude Fable 5.1.
🤖 Generated with Claude Code