chore(release): bump 0.1.0a1 → 0.1.0a2 for TestPyPI dry-run#4
Merged
Conversation
End-to-end validation of the Trusted Publishing pipeline that landed in PR #1 + the 15 TestPyPI Trusted Publishers configured today. Tagging this commit with `v0.1.0a2` will route through `publish-to-pypi`'s TestPyPI branch (per the `(a|b|rc)` regex on tag refs) and upload all 15 packages without any API token in repo secrets. Why not v0.1.0 yet: * 11 PyPI projects still don't exist (waiting on the new-project- creation rate limit window to clear); tagging v0.1.0 would route through the PyPI branch and fail-fast on the same 429s. * a2 → TestPyPI lets us verify OIDC + workflow wiring without touching the production namespace. The plugin dependency on the main package is unchanged at `"codemap-core>=0.1.0a1,<0.2"` — the lower bound a1 already admits a2 / a3 / b1 / rc1 / 0.1.x. Co-Authored-By: Claude Opus 4.7 (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.
Why
Validates the Trusted Publishing pipeline end-to-end:
publish-to-pypiworkflow (merged in PR feat(release): rename to codemap-core + Trusted Publishing pipeline #1) was never actually fired in CI0.1.0a2and tagging will route through the workflow's TestPyPI branch (per(a|b|rc)regex) and exercise the full OIDC publish pathWhat changes
Just version strings —
0.1.0a1→0.1.0a2in 15 `pyproject.toml` files (main + 14 plugins). The plugin dependency on the main package stays at"codemap-core>=0.1.0a1,<0.2"(lower bound a1 already covers a2 / a3 / b1 / rc1).What this does NOT touch
Test plan
🤖 Generated with Claude Code