chore: correct the version baseline to 0.2.0-SNAPSHOT-8-8-2026 - #112
Merged
Conversation
The garden-wide AI-first bump introduced this repository's first committed version reference and started it at 0.1.0-SNAPSHOT-8-8-2026, derived from an assumed 0.0.0 baseline. That overlooked the published release history: a v0.1.0 release already exists, so the committed version would have pointed behind what has already shipped. Rebased on the real baseline, the same 'minor bump while the major is 0' rule gives 0.2.0-SNAPSHOT-8-8-2026. Co-Authored-By: Claude Opus 5 (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.
Summary
The committed version reference is corrected from
0.1.0-SNAPSHOT-8-8-2026to0.2.0-SNAPSHOT-8-8-2026.The garden-wide AI-first bump created this repository's first committed version and
started it at
0.1.0-SNAPSHOT-8-8-2026, derived from an assumed0.0.0baseline. That overlooked thepublished release history — a v0.1.0 release already exists — so the committed version would have pointed
behind what has already shipped.
Applying the same "minor bump while the major is 0" rule to the real baseline gives
0.2.0-SNAPSHOT-8-8-2026.Drafted by Claude on behalf of Daniel Stephenson.