Sessions recover a stuck sandbox and a stale runtime on their own.
Fixed
- A session whose sandbox name was still held by an old archived sandbox could never get a new sandbox. It now provisions under a fresh name.
- Opening a session repairs a stale runtime immediately instead of waiting for the background check.
- A prompt parked while the sandbox restarts keeps its sandbox deadline through every retry.
- A Firefox browser-extension error no longer reaches error reporting.
What's Changed
- fix(sandbox): extend a parked prompt's box deadline through the retry ladder by @markokraemer in #7860
- fix(web): drop the Firefox cross-compartment onerror-chain failure by @markokraemer in #7862
- chore(release): staging VERSION → 0.13.40 [skip ci] by @github-actions[bot] in #7863
- chore(release): VERSION → 0.13.40 [skip ci] by @github-actions[bot] in #7864
- fix(reaper): auto-repair a stale runtime at session-open, not just in the background by @markokraemer in #7859
- fix(platinum): advance the dedup attempt on a persistent name_taken 409 by @markokraemer in #7866
- Promote main 651ac3e to staging by @markokraemer in #7868
- Release v0.13.40 — Stuck sandboxes recover by @github-actions[bot] in #7871
Full Changelog: v0.13.39...v0.13.40