Record what v0.19 shipped - #96
Merged
Merged
Conversation
Three defects on the path between a running cluster and a configured one, all found by staging the first real AWS apply rather than by running it. The README bump is in the same commit because it has to be: the lint added in v0.19 requires the README's version claim to name the newest row of this table. That is the first time it has bound a release, and it binds it the right way round — the roadmap row is the source of truth, and the tag comes after both. Co-Authored-By: Claude Opus 5 <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.
Step one of cutting v0.19: the Shipped row lands first, then the tag, so
the tagged tree already contains its own entry.
The three are #91, #94 and #93; #95 records how they were found.
The README bump is in the same commit because it has to be
This is the first release since the version lint (#90), which requires
the README's claim to name the newest row of the Shipped table. Adding
the row without the bump fails
tests/lint.That is the interaction working as intended, and in the right direction:
the roadmap table is the source of truth, the README follows it, and the
tag comes after both. The lint's tag half stays quiet here — a table
ahead of the tags is the normal state mid-release, and only a table
behind them is a release nobody wrote down.
🤖 Generated with Claude Code