chore: release as v0.5.2 — v0.5.1 tag was already published - #249
Merged
Conversation
…g was already published The v0.5.1 tag + GitHub Release were published on 2026-07-31 (f670a14), before the run_python work landed. Rewriting a public tag breaks reproducibility (fetched tags don't auto-update), so this release keeps the published v0.5.1 as-is and ships the new work as v0.5.2: - Restore the [0.5.1] section to exactly what the published tag contains (verified byte-identical) with its original 07-31 date - New [0.5.2] section: run_python persistence semantics + superseded artifact cleanup - Bump __version__ to 0.5.2 SPEC: 20260801-1122_run-python-unified-semantics Progress: release renumbered to v0.5.2 Next: merge → tag v0.5.2
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
1 participant
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.
Summary
While preparing the v0.5.1 tag, we found it was already published on 2026-07-31 (
f670a141, PR #240 merge) with its GitHub Release — before the run_python semantics work landed. This is exactly the numbering hazard documented in #246.Rewriting a public tag breaks reproducibility (fetched tags don't auto-update on clients), so the published v0.5.1 stays as-is and the new work ships as v0.5.2:
[0.5.1]changelog section to exactly what the published tag contains (verified byte-identical againstf670a141), with its original 07-31 date — reverts the section merge from docs: finalize CHANGELOG for v0.5.1 #248[0.5.2]section (2026-08-01): run_python persistence semantics unification + superseded PPTX artifact cleanup__version__to 0.5.2After merge,
v0.5.2will be tagged on the merge commit (tag push triggers the automated GitHub Release).