-
Notifications
You must be signed in to change notification settings - Fork 229
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
Remove cargo audit ignores once chrono advisory is resolved #4590
Comments
Note that chrono itself has the same issue, not just transitively via time. Chrono updating to time 0.3 by itself is not sufficient. |
Thank you! Looks like they have an issue for that: chronotope/chrono#499, adding it here for future reference. |
mhammond
added a commit
to mhammond/application-services
that referenced
this issue
Mar 28, 2023
mhammond
added a commit
to mhammond/application-services
that referenced
this issue
Mar 29, 2023
mhammond
added a commit
to mhammond/application-services
that referenced
this issue
Mar 29, 2023
mhammond
added a commit
to mhammond/application-services
that referenced
this issue
Mar 29, 2023
mhammond
added a commit
to mhammond/application-services
that referenced
this issue
Mar 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With #4589, we added
cargo audit
ignores for two security advisories. This ticket is to remove the ignoresThis means one of two things:
time
directlychrono
resolves the issue and releases a fixed version, upgrade to thatWe should do this once enough time has passed and/or:
┆Issue is synchronized with this Jira Task
┆Epic: Important backlog
The text was updated successfully, but these errors were encountered: