Open
Conversation
Cut'n'pasta error when I wrote the changelog.
After releasing `corepc-types 0.11.0` there was a fix that had to be done to `jsonrpc`. I then forgot to release `client` and `node`. Yesterday I released `client v0.11.0` but then when attempting the `node v0.11.0` release found it was broken because we did a bunch of API additions (and breaks) since `types` was released. - Bump `types` to `v0.12.0` - Bump `client` to `v0.12.0` - Bump `node` straight to `v0.12.0` skipping `v0.11.0` so it's version number stays in sync with the other two. FTR there is no need to yank `client 0.11.0` because it is functional and harmless.
tcharding
force-pushed
the
push-rvtxpmxpkxzo
branch
from
82eabb6 to
038508d
Compare
This was referenced Apr 13, 2026
Merged
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
2 participants
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.
After releasing
corepc-types 0.11.0there was a fix that had to be done tojsonrpc. I then forgot to releaseclientandnode.Yesterday I released
client v0.11.0but then when attempting thenode v0.11.0release found it was broken because we did a bunch of API additions (and breaks) sincetypeswas released.typestov0.12.0clienttov0.12.0nodestraight tov0.12.0skippingv0.11.0so it's version number stays in sync with the other two.FTR there is no need to yank
client 0.11.0because it is functional and harmless.