-
Notifications
You must be signed in to change notification settings - Fork 463
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
sec: Remove vulnerable time-0.1.x chrono dependency #884
Conversation
🦋 Changeset detectedLatest commit: 695e288 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
d28615d
to
d499c39
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
d499c39
to
956a433
Compare
956a433
to
a4e37cd
Compare
a4e37cd
to
4a45b5d
Compare
@Schniz is this something you can think might be merged, or should I close this PR and stop checking it? |
In trying to rerun the tests but I’m afk (parental leave) so I’m not sure why it failed. We can ignore clippy |
Oh, congrats!!! Will try to make build green then meanwhile! :D |
This dependency is optional for chrono and enabled by default for backward compatibility only. See: https://rustsec.org/advisories/RUSTSEC-2020-0071 See: https://github.com/chronotope/chrono/blob/v0.4.23/CHANGELOG.md#0416
f0c260f
to
695e288
Compare
addressed in another PR, thanks for the contribution 🙏 |
This dependency is optional for chrono and enabled by default for backward compatibility only.
See: https://rustsec.org/advisories/RUSTSEC-2020-0071
See: https://github.com/chronotope/chrono/blob/v0.4.23/CHANGELOG.md#0416