docs: the control commands ship in 1.3.0, not 1.2.3 - #121
Merged
Conversation
The version hedge named 1.2.3, which was right when it was written. The release prepared since is 1.3.0: pyproject says 1.3.0 and the CHANGELOG credits #79 there, naming capture status and capture stop as shipping for the first time. PyPI is still on 1.2.2 and no v1.3.0 tag exists, so the hedge stays and only the number changes.
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.
The README tells the reader that
capture status,capture stop, and thestatus_recording/stop_recordingcontract are not in the published wheel,and names the release that carries them. It named 1.2.3.
That number is now stale.
pyproject.tomlreads1.3.0, and the CHANGELOGcredits #79 under
## v1.3.0, describing those commands as shipping there forthe first time.
PyPI is still on 1.2.2 and there is no
v1.3.0tag yet, so the hedge itself isstill doing its job. Only the version number changes.