chore(ci): Move the self pins to v0.7.0 - #33
Merged
Merged
Conversation
The release pull request for 0.7.0 merged before the commit moving the pins reached its branch. So the v0.7.0 tag carries the version bump but its reusable workflows still call the v0.6.0 actions, and main has been red since, because the pins no longer name the version this tree is. This moves the pins, and the calls shown in the README, the quickstart, the examples and the workflows README, to v0.7.0. The actions at that tag are the current ones, so this is what the tag should have held. A 0.7.1 release will carry it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018ccJFsmZ4jAKYmFNgNBh9u
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
2 participants
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.
Why
The 0.7.0 release pull request (#32) merged about 20 seconds before the commit moving the pins reached
release/v0.7.0. So:v0.7.0is tagged and published, with the version bump but without the pin move.v0.6.0actions. That meansstrength.yml@v0.7.0misses the private-repository branch fix.aywrite/mache@v0.6.0, which has no root action.mache/__init__.py.What changed
Every
v0.6.0outside the changelog becomesv0.7.0, in 20 lines across 8 files:strength.yml,batch.ymlandcalibrate.yml.github/workflows/README.mdThe actions at the
v0.7.0tag are the current ones, so this is what the tag should have held.PyPI does not allow a version to be uploaded twice, and a moved tag would leave two releases under one name. So a 0.7.1 patch release will carry this, with its own pins moved to
v0.7.1before that release pull request merges.How it was checked
python3 -m pytest testspasses (470 tests), including the pin tests that read each pinned action at thev0.7.0tag.pre-commit run --all-filesis clean.🤖 Generated with Claude Code
https://claude.ai/code/session_018ccJFsmZ4jAKYmFNgNBh9u
Generated by Claude Code