-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Migrate off of chrono
to time
#9675
Comments
We might be able to translate |
Which is vulnerable to `RUSTSEC-2020-0071`. `chrono` seems to be no longer maintained so #9675 will be the real solution for that. The other dependencies should be able to be unpatched once they have a release removing the dependency. Signed-off-by: Jesse Szwedko <[email protected]>
Does the |
Yeah, that's a good point. It looks like not yet: time-rs/time#193 |
…9678) * chore(deps): Patch dependencies to remove dependency on `time` v0.1 Which is vulnerable to `RUSTSEC-2020-0071`. `chrono` seems to be no longer maintained so #9675 will be the real solution for that. The other dependencies should be able to be unpatched once they have a release removing the dependency. Signed-off-by: Jesse Szwedko <[email protected]>
Possible option: https://github.com/Yuri6037/time-tz |
|
Closing this since |
chrono
is lightly maintained these das (no release in a year nor responsive to issues, including security issues) and thetime
crate reportedly implements much of whatchrono
is used for.We should:
chrono
strftime
specifiers for parsing and formatting. Thetime
crate [does not support this] so we will need to implement it ourselves.This would resolve
RUSTSEC-2020-0071
.The text was updated successfully, but these errors were encountered: