Skip to content
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

Closed
tarikeshaq opened this issue Oct 19, 2021 · 2 comments
Closed

Remove cargo audit ignores once chrono advisory is resolved #4590

tarikeshaq opened this issue Oct 19, 2021 · 2 comments

Comments

@tarikeshaq
Copy link
Contributor

tarikeshaq commented Oct 19, 2021

With #4589, we added cargo audit ignores for two security advisories. This ticket is to remove the ignores

This means one of two things:

  • Either remove chrono all together and use time directly
  • If chrono resolves the issue and releases a fixed version, upgrade to that

We should do this once enough time has passed and/or:

┆Issue is synchronized with this Jira Task
┆Epic: Important backlog

@jhpratt
Copy link

jhpratt commented Oct 19, 2021

Note that chrono itself has the same issue, not just transitively via time. Chrono updating to time 0.3 by itself is not sufficient.

@tarikeshaq
Copy link
Contributor Author

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants