Every dev dependency moves to the newest release that has been public for at least 7 days, and that rule is now enforced rather than remembered: .npmrc sets min-release-age=7 and Dependabot gets a 7-day cooldown on both ecosystems. `npm ci` was verified to ignore the age rule for versions already in the lockfile, so it only shapes what gets locked. vitest / coverage-v8 4.1.10 -> 5.0.5 (suite passed unchanged) @biomejs/biome 2.5.5 -> 2.6.2 (exact) svelte 5.56.8 -> 5.57.2 vite-plugin-svelte 7.2.0 -> 7.3.1 svelte-check 4.7.4 -> 4.7.7 jsdom 30.0.1 -> 30.1.3 (dom-environment canary first) knip 6.29.0 -> 6.42.1 wxt 0.21.3 -> 0.21.4 (+ transitive vite 8.3.5) npm audit: 13 (7 high) -> 3 low, all one deepmerge advisory with no fixed release, inside vite-plugin-svelte's dev-time option merging; documented in docs/09 §3.1. --omit=dev stays 0. This supersedes Dependabot #19-#25. The six-entry overrides block is deleted: none of those packages is in the tree any more (WXT 0.21 dropped web-ext-run, Vite 8 bundles with rolldown), and a stale override would silently pin a package the day it came back. WXT got the built-manifest diff the 2026-08-03 decision requires: identical keys and values apart from the deliberate minimum_chrome_version, identical file inventory. Biome 2.6 began formatting Markdown and YAML, so both are excluded rather than letting a formatter reflow hand-written docs. dependabot.yml now keeps WXT out of the routine group and ignores majors of the TypeScript pair and @types/node. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 lines
387 B
Plaintext
7 lines
387 B
Plaintext
# Supply-chain cooldown (docs/01 §6): resolve every install to the newest
|
|
# release that has been public for at least 7 days. Malicious versions
|
|
# published to npm have historically been caught and pulled within hours to
|
|
# days; a week of age keeps this repo out of that window. Units are DAYS.
|
|
# Dependabot applies the same rule through `cooldown` in dependabot.yml.
|
|
min-release-age=7
|