Repository navigation
docs: document all eight changes since v0.1.0, and cut 0.1.1 - #32
Merged
Merged
Conversation
The Unreleased section described four of the eight commits merged since the tag. The four it omitted are the ones a prospective contributor most needs: there is now a contributing guide, a roadmap, and a production guardrail check, and the changelog said none of that existed. - Opened a real `## [0.1.1]` heading and bumped pyproject to match, so the version the changelog releases and the version the wheel carries agree. - Added the missing entries: production intent guardrails (#5, #6), the contributing guide (#18), the roadmap with its CI-enforced stack count (#28), and the removal of the stale README test figures (#17, #20). - Removed "Twelve tests" and "64 resources to add" from Unreleased. That is #20 recurring in the one file that change did not cover. A number in a released entry is a dated snapshot and may stand; a number in Unreleased is not yet history and was simply wrong. - Replaced them with the gates that are actually enforced: the 88% coverage floor on 3.10/3.11/3.12, and the release workflow asserting on the published artifact that guardrails still refuse an 0.0.0.0/0 database and that the generated output carries no literal credential. - Stated plainly that there is no `terraform plan` in the release workflow. The eks+rds plan was run by hand, and a figure from a manual run is exactly what this entry declines to quote. Filed #31 to automate it. - ROADMAP: the same 64-resource claim, in the present tense, replaced with what CI does verify. Verified: pytest 91 passed, coverage 90.90% against the 88% floor. Closes #30 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.
Release documentation for 0.1.1. No code changes;
pyproject.tomlversion bump only.The gap
Four of eight. The four omitted are the ones that matter most to someone deciding whether to contribute: the guide, the roadmap, and the guardrail check.
The stale figures, which are the more interesting half
Unreleasedsaid "Twelve tests" and "64 resources to add, 0 to change, 0 to destroy". The suite is 91.This is #17 recurring. #20 removed exactly these numbers from the README, for the stated reason that "rewriting the numbers would only reset the clock; they drifted because nothing kept them true", and replaced them with a CI-enforced coverage floor. The changelog was not in scope for that change and drifted identically.
The distinction this PR draws: a number in a released entry is a dated snapshot and may stand. A number in
Unreleasedis not yet history, and was simply wrong. So the counts are gone and what replaces them is the gate:0.0.0.0/0database, and that generated output contains no literal credentialOne claim I wrote and then had to remove
My first draft said the release workflow "runs a real
terraform planbefore publishing". It does not:The
eks+rdsplan was run by hand. The changelog now says that outright, since a figure from a manual run is precisely the kind of number the same entry declines to quote. Automating it is #31, filed with three credential-free options and an acceptance criterion that requires reverting the #12 fix and watching the new job go red.That gap is worth stating plainly: four of the five defects fixed in this release were apply-breaking,
terraform validatewas green for all four, and nothing in CI would catch the fifth.Verification
Closes #30
🤖 Generated with Claude Code
https://claude.ai/code/session_012fMM2HhoJ2XzDkfMR2HwSa