Conversation
We released with a TBD in the deprecation notice. Fix it and bump the patch version so we can do a point release. Add a changelog entry and update the lock files. Full disclosure, the release tracking PR for 1.3.0 was done by me so this is my fail.
Member
Author
|
Found while working on #254 |
tcharding
marked this pull request as draft
September 17, 2026 02:45
Member
Author
|
Maybe we don't want this: #254 (comment) |
Member
|
I think we can do it. I don't think we should yank 1.3.0 regardless, so we should fix CI and follow through with this one. |
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.
We released with a TBD in the deprecation notice. Fix it and bump the patch version so we can do a point release.
Add a changelog entry and update the lock files.
Full disclosure, the release tracking PR for 1.3.0 was done by me so this is my fail.