Repository navigation
Conversation
The field's own comment says it tracks the next git tag, and the tags are the version of record. It had drifted two releases behind: v2.18.0 and v2.19.0 were both cut while it still read 2.17.0, so anyone reading the file for the current version got an answer two releases stale. No behaviour change -- consumers pin tags, not this field. Restoring it so the comment stays true. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing as obsolete. #72 (tagged v2.27.0) already set |
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.
The field's own comment says it tracks the next git tag. It had drifted two releases behind — v2.18.0 and v2.19.0 were both cut while it still read 2.17.0.
No behaviour change; consumers pin tags, not this field.
🤖 Generated with Claude Code