Repository navigation
release 0.7.0: the version the A0 work goes out under - #21
Merged
Merged
Conversation
0.6.0 was released on 2026-10-19 (tag v0.6.0, 8a65119, on PyPI) and the A0 work landed on top of the same number: yesterday's release prep edited the 0.6.0 section in place, moving its date to 2026-10-29, rewriting its intro to name macula-go v0.29.0, and appending two subsections to a release that had shipped. This restores that section to exactly what the tag's own CHANGELOG says — verified by comparing the block at v0.6.0 against the block here, byte for byte — and puts the new material in a `## 0.7.0 (2026-10-29)` section above it, with the A0 re-seal and the docs type-check as `### Changed`, and the honesty text ("what this release does not change") carried over unchanged because it is still true. pyproject's version is 0.7.0, which is what release.yml's guard compares the tag against. The README gains the same paragraph, and `pip install macula-py` resolves 0.7.0. Raf's ruling, 2026-10-29: py goes out as 0.7.0. Co-Authored-By: Claude Code <noreply@anthropic.com>
…claiming 0.6.0 resolves Mercurius r=1, two findings, both his. 1. 0.7.0's intro said the code is 0.6.0rc4's "plus the entries below", and the entries named nothing that touched src/. They had to: 24c1b39 (21 Oct) extracted helpers in src/macula_py/_wire.py and _blocking.py to meet the structural floor (+42/-16), so the code is not 0.6.0's unchanged. The intro now says 0.6.0's plus the entries below, and there is an entry for that change: helpers extracted, no baseline and no inline disables, the error a caller sees unchanged. 2. The README's 19 Oct banner said `pip install macula-py` resolves 0.6.0 directly under the new paragraph saying it resolves 0.7.0. Past tense now: "resolved 0.6.0 until 0.7.0". Co-Authored-By: Claude Code <noreply@anthropic.com>
This branch was successfully deployed
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.6.0 record says what 0.6.0 actually was.
0.6.0 was released on 2026-10-19 (tag
v0.6.0, 8a65119, on PyPI since 2026-10-19T18:32Z) and the A0 work landed on top of the same number. Yesterday's release prep then edited that shipped section in place: date moved to 2026-10-29, intro rewritten to name macula-go v0.29.0, two subsections appended to a release that had already gone out.This PR
CHANGELOG.md: the## 0.6.0 (2026-10-19)section is restored byte for byte to the tag's own CHANGELOG (compared programmatically), and the new material goes into## 0.7.0 (2026-10-29)above it — the A0 re-seal and the docs type-check as### Changed, with the "what this release does not change" text unchanged because it is still true.pyproject.toml:version = "0.7.0", which is exactly whatrelease.yml's guard compares againstv$versionon the tag.README.md: one paragraph for 0.7.0, including thatpip install macula-pyresolves it and that sealing stays preferred rather than required.No code changes.
Registry check, before review
v0.7.0does not exist locally or on origin;pypi.org/pypi/macula-py/0.7.0/jsonanswers 404, and the same endpoint answers 200 for 0.6.0 (positive control: the method finds a version that does exist).Raf's ruling, 2026-10-29: py goes out as 0.7.0, tag after green main CI.
🤖 Generated with Claude Code