Explore application-typed handshake rejection codes - #403
Merged
Conversation
wernst
approved these changes
Aug 25, 2026
Mayank808
added a commit
that referenced
this pull request
Aug 25, 2026
## Why River 0.221.0 includes the new application-typed handshake rejection code API from #403. ## What changed Bumps the `@replit/river` package version from 0.220.1 to 0.221.0. This prepares the package metadata for the next minor npm release. ## Versioning - [ ] Breaking protocol change - [ ] Breaking ts/js API change
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.
Why
Exploration PR, alternative to #401. This sketches application-typed handshake rejection codes: applications declare their codes as a tuple of TypeBox literal schemas,
validatemay return them, and they travel in the handshake response'scodefield with compile-time checking on both peers.The generics are parameterized on the schema tuple itself (
ReadonlyArray<TLiteral<string>>), never on barestringunions — the code type is derived from the schemas, so this shape works end to end:Versioning