chore: bump to 2.3.1-dev after cutting 2.3.0 - #367
Merged
Merged
Conversation
Post-release bump, immediately after the tag, so main never sits on a released version: a build from main would otherwise report 2.3.0 and be indistinguishable from the release itself. Note for consumers gating on this: _ver_lt strips everything after the first '-', so 2.3.1-dev compares EQUAL to 2.3.1. A `>= X.Y.Z` test is satisfied by every commit on that dev line, including ones predating whatever the consumer is actually looking for. Probe the capability -- a key in --print-schema's tier lists, a field in --print-state, or a member of manifest.top_level_keys / manifest.agent_args_compose -- not the number. 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.
Routine post-release bump, immediately after the
v2.3.0tag, somainnever sits on a released version — a build frommainwould otherwise report2.3.0and be indistinguishable from the release.One line:
SANDY_VERSION2.3.0→2.3.1-dev.For anyone gating on this number:
_ver_ltstrips everything after the first-, so2.3.1-devcompares equal to2.3.1. A>= X.Y.Ztest is satisfied by every commit on that dev line, including ones predating the feature being looked for. Probe the capability instead — a key in--print-schemas tier lists, a field in--print-state, or membership ofmanifest.top_level_keys/manifest.agent_args_compose.🤖 Generated with Claude Code