Repository navigation
Talos 0.20.0-rc.1 — First stable release candidate
Pre-releaseFirst release candidate for stable 0.20.0. The runtime retains Beta.9 behavior, including clear reply receipts and conversation-scoped pending-job counts. The operator contract, kernel and approval boundaries are unchanged.
Release qualification now requires an explicit upgrade predecessor and scans all four dependency locks. The stable-readiness guide defines platform, artifact, delivery, recovery and operating-observation gates.
Qualification before publication:
- macOS Python 3.12/3.13: 3,563 tests passed, 3 explicit skips per run (Linux-only bubblewrap, no in-tree venv in the source checkout, no private Git remote); native Linux/macOS Python 3.11 CI.
- 277 adversarial cases and 44 real-model E2E cases against the candidate archive.
- Signed clean installation and Beta.9 → RC.1 upgrade, schedule migration and rollback on macOS and ARM64 Linux.
- SHA-256, pinned Ed25519 verification and tamper rejection; four dependency locks and installed environments scanned with OSV, 0 findings. Public hygiene and changed-source secret scan pass; historical synthetic/public-key findings remain unchanged.
Stable is not released: it requires seven consecutive calendar days on a deployed RC, investigation of operational errors, and qualification of the final stable artifact. This CLI release does not certify a notarized desktop app.
The local pre-publication rehearsal initially used an unescaped file URL and a relative artifact directory; corrected invocation paths passed. These were harness invocation errors, not relaxed verification.
The first ARM64 clean-install attempt found a test fixture inheriting group-writable permissions from umask 0002. Its fixture now sets mode 0600 explicitly; insecure real skill files are still refused. The failed attempt is retained and the corrected artifact requalified.