chore: update h3 and srvx - #464
Merged
Merged
Conversation
Member
Contributor
|
@Fdawgs this was 100% human 😄 (pi0x account is used in my dev container) |
pi0x
marked this pull request as ready for review
July 21, 2026 15:58
Fdawgs
approved these changes
Jul 21, 2026
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
3 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.
This PR updates srvx and H3 to the latest versions.
I have double checked that both fixtures by default are emitting
content-typeheader for parity now.h3-router is removed since
H3instance in v2 itself is a router.Checklist
npm run test && npm run benchmark --if-present(running now)and the Code of conduct