-
Notifications
You must be signed in to change notification settings - Fork 375
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
Add axum-core
DoS
#1417
Add axum-core
DoS
#1417
Conversation
Could the CI error be because it doesn't handle parsing |
Co-authored-by: pinkforest(she/her) <36498018+pinkforest@users.noreply.github.com>
Looks like it, but I'm not familiar with that part of the code base. I'm
hoping someone else who knows it better will chime in.
…On Sun, Sep 11, 2022 at 11:59 AM David Pedersen ***@***.***> wrote:
Could the CI error be because it doesn't handle parsing rc versions like
0.3.0.rc.2?
—
Reply to this email directly, view it on GitHub
<#1417 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBBAWS5ACAC3ZWXNEELV5X6XFANCNFSM6AAAAAAQJ2I534>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
The decision we ended up last month with was here: #1417 (comment) patched = [">= 0.2.8, < 0.3.0-rc.1", ">= 0.3.0-rc.2"] And it links to the issue on rustsec/rustsec we clarified the SemVer out: rustsec/rustsec#690 (comment) Which reflects the (eventually) merged PR. We discussed also in zulip re: this: I'll TODO to document this properly. |
No description provided.