Repository navigation
release 0.10.0: the version the A0 work goes out under - #22
Merged
Merged
Conversation
0.9.0 was released on 2026-10-19 (tag v0.9.0, 8b98cdf, 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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs the 29 Oct release batch.
Purpose (reliability): the A0 work reaches users under a version number that has not already been published, and the 0.9.0 record says what 0.9.0 actually was.
0.9.0 was released on 2026-10-19 (tag
v0.9.0, 8b98cdf, on Packagist) and the A0 work landed on top of it without moving the number. Yesterday's release prep then edited that shipped section in place: its date became 2026-10-29, its intro named macula-go v0.29.0, and two subsections were appended to a release that had already gone out.This PR
CHANGELOG.md: the## [0.9.0] - 2026-10-19section is restored byte for byte to what the tag's own CHANGELOG holds (compared programmatically, not by eye), and the new material goes into## [0.10.0] - 2026-10-29above it — the A0 re-seal and the structural-floor gate as### Changed, and the "what this release does not change" text carried over unchanged because it is still true.README.md: one paragraph for 0.10.0, including that a defaultcomposer require macula-io/macula-phpresolves it and that refusing a clear call unless the caller opts out is still not in this release.No code changes. php carries no version string in the tree — Packagist takes it from the tag — so there is nothing else to bump.
Registry check, before review
v0.10.0does not exist locally or on origin;p2/macula-io/macula-php.jsonlists nov0.10.0, and listsv0.9.0(positive control: the method finds a version that does exist).Raf's ruling, 2026-10-29: php goes out as 0.10.0, tag after green main CI.
🤖 Generated with Claude Code