NetScript 0.0.8-canary.8

NetScript 0.0.8-canary.8

What this canary is for. canary.8 is release candidate 8 for NetScript 0.0.8. It bundles 0 pull requests since the previous canary point so downstream apps can try the published packages before 0.0.8 ships. It is a pre-release: normal semver resolution never selects it, and Latest stays v0.0.7. All 35 @netscript/* packages are published at exactly 0.0.8-canary.8. The canary publish and version-pinned production E2E both passed (publish, production E2E).

Highlights

No included pull requests.

Breaking changes and migration

No breaking changes declared by included PRs.

Known open follow-ups

No referenced issues remain open.

Trying this canary

Pin exact versions, for example jsr:@netscript/service@0.0.8-canary.8. Deno applies a default 24-hour minimum dependency age. For testing a newer canary, set minimumDependencyAge: 0 in the consumer configuration; this changes admission timing, not versions.

PRs listed below as "closes no linked issues" may deliver partial scope. Their explicitly referenced open issues are listed above; remaining scope stays tracked on those issues.

---

Canary payload derived from merge-aware history after 370b70d29a1e4b3f28851f4700b0e7d59e4f231f (0 commit(s) inspected; outcome: genuine-empty).

Included pull requests

Genuine empty payload: no commits landed since the previous canary point.

Coordinator addendum: what canary.8 contains

canary.8 re-qualifies the exact content of canary.7 (370b70d29, identical tree). canary.7 published completely, but its pinned production E2E hit a transient JSR 502 on one package file, tracked as #2379. Its included pull requests and breaking changes are in the canary.7 notes: Deno 2.9.7 (#2368), watch(keys, { initial: true }) (#2371), Redis delayed promotion exactly-once (#2360), atomic saga capability through the projection (#2363), the cron fixes (#2357, and the breaking weekday translation #2359), the bounded-runner pipe fix (#2372) and the release-preflight CI gate (#2378). canary.8's production E2E passed: scaffold.runtime 119/0/1 and quickstart.walk 9/0.

Upgrade note: Deno 2.9.7 and existing lock files

This canary moves NetScript's toolchain, CI and scaffold to Deno 2.9.7 (#2368). Deno 2.9.6 changed how npm package IDs with single-resolution peers are written (denoland/deno#36608). A deno.lock written by Deno 2.9.5 or older still passes --frozen on 2.9.6+, but can then fail at runtime with ERR_MODULE_NOT_FOUND on a path ending in _1.

If your project's lock was written by Deno ≤2.9.5, refresh it after upgrading: run deno install --lockfile-only with Deno 2.9.7, plus your project's own lock task for any nested workspace lock. The refresh rewrites ID format only; resolved versions stay the same.

Note for third-party KV adapters

@netscript/kv/testing (#2371) runs the new initial-snapshot and ready scenarios only for adapters that declare support for them. Adapters without them still pass the default-path contract. WatchableKvBridge expects the wrapped adapter to honour watch(keys, { initial: true }); every first-party adapter does. The fallback for adapters that don't is tracked in #2377.