Remove chrono #211
Closed
Remove chrono #211
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since RUSTSEC has been flagging up the vulnerabilities in chrono and the older time versions recently, our
cargo auditworkflow is grumbling about things quite a bit.simple_asn1has been updated to remove dependencies onchronoin favour of thetimecrate (which has had major feature updates), so I have updated that to the next minor version. I've also removedchronofrom dev-dependencies and reworked the example to usetime.cargo auditdoesn't complain about vulnerabilities any more.