Repository navigation
release: 0.1.2 - #35
Merged
Merged
Conversation
0.1.1 was tagged on 2026-09-04 and never published. Its release run failed at test-wheel on all three Pythons and correctly published nothing, to TestPyPI or PyPI, so PyPI has sat on 0.1.0 for sixteen days while master carried nine merged changes. The cause was in the workflow, not the package. It asserted `publicly_accessible = false` with a single space; create_db_subnet_group joined that block in #13 and terraform fmt realigned it to four. Red since 2026-07-31, unnoticed, because a workflow that runs only on a tag push has no feedback loop between tags. #33 fixed it in 4e862a1. Package contents are identical to what 0.1.1 would have published, plus the workflow fix. v0.1.1 is left in place as a git tag rather than deleted or moved. It records that a release was attempted and refused, which is a true thing that happened, and the changelog says so under its own heading rather than quietly renumbering. Verified: pytest 91 passed, coverage 90.90% against the 88% floor, ruff clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012fMM2HhoJ2XzDkfMR2HwSa
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.
PyPI has been on 0.1.0 since 2026-07-29 while
mastercarried nine merged changes. This unblocks that.What happened to 0.1.1
Tagged 2026-09-04. The release run failed at
test-wheelon 3.10, 3.11 and 3.12 and published nothing, not to TestPyPI and not to PyPI. The gating worked exactly as designed; the thing it gated on was wrong.The cause was in the workflow, not the package:
create_db_subnet_groupis 22 characters, joined that block in #13, andterraform fmtrealigned the attribute to four spaces. The workflow had been red since 2026-07-31 and nothing noticed, because it runs only on a tag push and no tag was cut in that window. #33 fixed it in 4e862a1.The generated output was correct throughout: the database was private, prod
deletion_protectionwas true.Why 0.1.2 rather than re-tagging 0.1.1
v0.1.1stays where it is, as a git tag pointing at a commit that was never published. It records that a release was attempted and refused, which is a true thing that happened. Moving or deleting it would make the history tidier and less accurate, and this repo is not in the business of that trade.The changelog says so plainly, under 0.1.1 own heading:
Package contents are identical to what 0.1.1 would have published, plus the workflow fix.
Verification
The real test is the release run itself, which is what failed last time and which this PR exists to let succeed.
🤖 Generated with Claude Code
https://claude.ai/code/session_012fMM2HhoJ2XzDkfMR2HwSa