chore(release): v0.1.2 — migration safety - #44
Merged
Conversation
Moves both version declarations to 0.1.2, dates the changelog entry, and points the README install pins and version table at the new tag. Co-Authored-By: Claude Opus 5 (1M context) <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
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.
Release prep for v0.1.2, same shape as #38 did for v0.1.1: version and README land on
devfirst, then thedev→mainpromotion PR.pyproject.tomlandcurator.__version__both move to0.1.2— the drift test added in v0.1.1 fails if only one moves.CHANGELOG[Unreleased]becomes[0.1.2] — 2026-07-28, with its tag link.v0.1.2; v0.1.1 becomes Previous.The tag
v0.1.2does not exist yet — it is pushed immediately after thedev→mainmerge, per CONTRIBUTING.🤖 Generated with Claude Code