TypeScript 7 is the native port — a rewrite of the compiler, not a version bump. Dependabot has raised it twice and it failed both times:
Both are now ignored in .github/dependabot.yml, per-ecosystem (root and /web are separate entries — scoping the first ignore to the root only is precisely why #64 appeared). Minor and patch TS updates continue to flow.
Why an issue
An ignore rule with no tracking issue is how a dependency quietly rots. This exists so the migration is scheduled deliberately and the ignores are lifted on purpose.
When picking this up
- Remove the
typescript major ignore from both npm entries in .github/dependabot.yml
- Expect real work in
src/ (the SDK, which the redaction-proof tests gate) and in web/
- The executable-repro proof (
scripts/prove-repro-executes.mjs) is a hard gate — the compiled output must still run in Chromium
Not urgent: TypeScript 5.9 is supported and nothing is blocked on it.
TypeScript 7 is the native port — a rewrite of the compiler, not a version bump. Dependabot has raised it twice and it failed both times:
web/) — failed the web type-checkBoth are now ignored in
.github/dependabot.yml, per-ecosystem (root and/webare separate entries — scoping the first ignore to the root only is precisely why #64 appeared). Minor and patch TS updates continue to flow.Why an issue
An ignore rule with no tracking issue is how a dependency quietly rots. This exists so the migration is scheduled deliberately and the ignores are lifted on purpose.
When picking this up
typescriptmajor ignore from both npm entries in.github/dependabot.ymlsrc/(the SDK, which the redaction-proof tests gate) and inweb/scripts/prove-repro-executes.mjs) is a hard gate — the compiled output must still run in ChromiumNot urgent: TypeScript 5.9 is supported and nothing is blocked on it.