Skip to content

Release 1.0.0: changelog section and the plan's record #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tap merged 1 commit into from
Oct 2, 2026
Merged

Release 1.0.0: changelog section and the plan's record #36

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,17 @@
# Changelog

Changes to the Python class contract and to the object's behavior, newest first. Before 1.0,
breaking changes to the contract are allowed where they buy correctness (D5 in
`docs/PRODUCTION-PLAN.md`); each is recorded here.
breaking changes to the contract were allowed where they bought correctness (D5 in
`docs/PRODUCTION-PLAN.md`); each is recorded here. From 1.0.0, a change to the class contract is
a major version.

## Unreleased
## 1.0.0 — 2026-10-01

The first stable release: the class contract as the ReadMe states it, the production plan's
Phases 0–5 and 8 complete, and Phase 6 validated in Max on Intel. Still to run in a Max session
(plan 8.8): the runtime-test steps added in this cycle, the Windows checks of 6.4, and the arm64 and
Windows release zips of 6.5 — the first 1.0.x work. The packages are unsigned until signing
credentials exist (ReadMe: clear the quarantine once on a Mac).

### Changed — type hints map as a reader expects

Expand Down
10 changes: 7 additions & 3 deletions docs/PRODUCTION-PLAN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -744,7 +744,11 @@ down rather than discovered again. *This plan was itself audited before being ad
repeat the runbook's step 4 on the release packages, and tag `v0.11.0`.

*The 1.0 gate (revised):* 8.1–8.6 change what the ReadMe promises or what a class can rely on, so
they land before 1.0, where D5 still allows them; 8.7 may follow it.
they land before 1.0, where D5 still allows them; 8.7 may follow it. *Decided 2026-10-01 (the maintainer):*
**1.0.0 is tagged with 8.1–8.7 merged (#35) and 8.8 outstanding** — the contract changes are in, and
what 8.8 verifies in Max is behavior the core battery and the glue test already pin on Linux. 8.8,
the Windows half of 6.4 and the unchecked zips of 6.5 are the first 1.0.x work; the release is a
draft until signing exists, as `release.yml` has it.

## Phase 7 — plugin front ends (optional, post-1.0)

Expand All @@ -765,8 +769,8 @@ they land before 1.0, where D5 still allows them; 8.7 may follow it.
9. Phase 6 — in-Max validation before tagging 1.0.
10. Phase 4.7–4.8 — uv for the tooling, then one package for every platform on each tag.
11. Phase 8 — the audit's findings, in the order above: 8.1 (docs and hardening, first, so the
ReadMe stops overclaiming while the fixes land), 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, then the Mac
session 8.8 — all before 1.0.
ReadMe stops overclaiming while the fixes land), 8.2, 8.3, 8.4, 8.5, 8.6, 8.7 (#35), then the
Mac session 8.8 — decided on 2026-10-01 to follow 1.0.0 rather than gate it.

## External prerequisites

Expand Down
Loading