From b78160c7e4baf00cdbd0ed0522dc08dc26c1c4d8 Mon Sep 17 00:00:00 2001 From: beamologist Date: Thu, 29 Oct 2026 02:58:12 +0100 Subject: [PATCH 1/2] release 0.10.0: the version the A0 work goes out under MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 0.9.0 was released on 2026-10-19 (tag v0.9.0, 8b98cdfd, on Packagist) and the A0 work landed on top of it without moving the number, so yesterday's release prep edited the 0.9.0 section in place: its date became 2026-10-29, its intro was rewritten to name macula-go v0.29.0, and two subsections were appended to a release that had already shipped. This restores that section to exactly what the tag's own CHANGELOG says — verified by comparing the block at v0.9.0 against the block here, byte for byte — and puts the new material where it belongs: a `## [0.10.0] - 2026-10-29` section above it, with the A0 re-seal and the structural-floor gate as `### Changed`, and the honesty text ("what this release does not change") carried over unchanged because it is still true. The README gains the same paragraph: 0.10.0 resolves by default, and refusing a clear call unless the caller opts out is still not in this release. Raf's ruling, 2026-10-29: php goes out as 0.10.0. Co-Authored-By: Claude Code --- CHANGELOG.md | 21 ++++++++++++++------- README.md | 8 ++++++++ 2 files changed, 22 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 527a928..d79b330 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,15 +8,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] -## [0.9.0] - 2026-10-29 +## [0.10.0] - 2026-10-29 -The wire 1.0 release, for the fleet's flag day (19 Oct 2026, 18:03 UTC): from -then on every live station speaks wire 1.0 (macula 15) and nothing older, and -0.8.2 can no longer connect. libmacula is macula-go v0.29.0, the release that -carries the A0 contract (v0.27.0 at the flag day); this package's code is -0.9.0-rc.6's. The entries for rc.1 to rc.6 below are what changed since 0.8.2. +The A0 release: libmacula is macula-go v0.29.0, the release that carries the A0 +contract where 0.9.0 shipped v0.27.0, and a call a keyed provider refuses +`sealed_required` is now resealed and answered. No wire change: this package's +code is 0.9.0-rc.6's plus the entries below. -### Changed since this entry was written +### Changed - **A call a keyed provider refuses `sealed_required` is resealed and answered**, instead of the caller failing on a stale keyless candidate: the caller seals again to the key in the refusal's @@ -40,6 +39,14 @@ carries the A0 contract (v0.27.0 at the flag day); this package's code is `serveStream` take the policy as a nullable parameter, and omitting it serves any caller (macula-php#19 for streams, macula-php#21 for unary). +## [0.9.0] - 2026-10-19 + +The wire 1.0 release, for the fleet's flag day (19 Oct 2026, 18:03 UTC): from +then on every live station speaks wire 1.0 (macula 15) and nothing older, and +0.8.2 can no longer connect. libmacula is macula-go v0.27.0, whose code is +v0.27.0-rc.8's; this package's code is 0.9.0-rc.6's. The entries for rc.1 to +rc.6 below are what changed since 0.8.2. + ## [0.9.0-rc.6] - 2026-10-17 ### Added diff --git a/README.md b/README.md index c2e533b..3a37eb6 100644 --- a/README.md +++ b/README.md @@ -20,6 +20,14 @@ --- +> **A0, 0.10.0 (2026-10-29):** over libmacula from macula-go v0.29.0. A call a +> keyed provider refuses `sealed_required` is now resealed to the key that +> refusal carries and answered, instead of failing on a stale keyless candidate. +> Sealing is still the default only where the provider names a KEM key, and a +> procedure served with no policy is still open; refusing a clear call unless the +> caller opts out is not in this release. A default +> `composer require macula-io/macula-php` resolves 0.10.0. +> > **Wire 1.0, 0.9.0 (2026-10-19):** it speaks wire 1.0 (macula 15) and nothing > older, so it reaches only a wire 1.0 station. The fleet moved to wire 1.0 on 19 Oct 2026 at 18:03 UTC, and from then on 0.8.2 and everything before it > can no longer connect. A default `composer require macula-io/macula-php` From 93baca71a057ea1e0e143b5ca234c84f32a49c2b Mon Sep 17 00:00:00 2001 From: beamologist Date: Thu, 29 Oct 2026 03:06:37 +0100 Subject: [PATCH 2/2] readme: the 0.9.0 banner says what 0.9.0 resolved, not what it resolves MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mercurius r=1: the new paragraph says a default `composer require` resolves 0.10.0 and the 19 Oct banner four lines below said it resolves 0.9.0. Two contradicting claims about the same command. The older one is now past tense — "resolved 0.9.0 until 0.10.0" — which keeps the history and stops asserting it today. Co-Authored-By: Claude Code --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3a37eb6..c64fd8a 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,7 @@ > **Wire 1.0, 0.9.0 (2026-10-19):** it speaks wire 1.0 (macula 15) and nothing > older, so it reaches only a wire 1.0 station. The fleet moved to wire 1.0 on 19 Oct 2026 at 18:03 UTC, and from then on 0.8.2 and everything before it > can no longer connect. A default `composer require macula-io/macula-php` -> resolves 0.9.0. +> resolves 0.9.0 until 0.10.0. > > **Status, 2026-10-14:** over macula-go's **released** libmacula (the tag in > `abi/MACULA_GO_REF`, ABI 1), so on wire 1.0 (macula 15): handshake v5 bound to