-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dependendencies: bump to hyper 1.0.0 #726
Merged
Merged
Conversation
This file contains 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
Skipping CI for Draft Pull Request. |
istio-testing
added
do-not-merge/work-in-progress
Block merging of a PR because it isn't ready yet.
needs-rebase
Indicates a PR needs to be rebased before being merged
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
labels
Nov 16, 2023
howardjohn
force-pushed
the
deps/hyper-1.0.0
branch
from
November 16, 2023 00:36
0c82a99
to
ad0009b
Compare
istio-testing
added
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
and removed
needs-rebase
Indicates a PR needs to be rebased before being merged
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
labels
Nov 16, 2023
Hyper boring was superseded by cloudflare/boring#194 so the closed PR shown right now isn't a blocker. |
istio-testing
added
the
needs-rebase
Indicates a PR needs to be rebased before being merged
label
Dec 23, 2023
istio-policy-bot
added
the
lifecycle/automatically-closed
Indicates a PR or issue that has been closed automatically.
label
Feb 14, 2024
howardjohn
force-pushed
the
deps/hyper-1.0.0
branch
from
February 14, 2024 16:24
ad0009b
to
22cb1c8
Compare
istio-testing
removed
do-not-merge/work-in-progress
Block merging of a PR because it isn't ready yet.
needs-rebase
Indicates a PR needs to be rebased before being merged
labels
Feb 14, 2024
stevenctl
approved these changes
Feb 23, 2024
What's the reasoning for/against |
/retest |
howardjohn
force-pushed
the
deps/hyper-1.0.0
branch
from
February 23, 2024 19:21
6b80615
to
fd6f3db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lifecycle/automatically-closed
Indicates a PR or issue that has been closed automatically.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
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.
Two forks left:
This trades forks on: boring, hyper-util
For forks on: boring, tower-hyper-http-body-compat
So technically its a 1:1 tradeoff, but this is more future proof and http-body-compat is much smaller than hyper-util. IMO this is good to go for now
Fixes #805