Update Chrono Dependency once the CVE is fixed

ben commented

2022-04-12 17:11:40 +02:00

Owner

We currently ignore the CVE Warning in cargo deny, as we should not be using the problematic code path.
Still it would be preferable to not use a bugged version.
A fix is currently in the works and we should update once that is merged and a new release has been cut.

We currently ignore the CVE Warning in cargo deny, as we should not be using the problematic code path. Still it would be preferable to not use a bugged version. A fix is currently in the works and we should update once that is merged and a new release has been cut. - [x] [Upstream Issue][chrono-499] - [x] [Upstream Bug-Fix PR][chrono-677] - [x] [Next Release][chrono-674] [chrono-499]: https://github.com/chronotope/chrono/issues/499 [chrono-677]: https://github.com/chronotope/chrono/pull/677 [chrono-674]: https://github.com/chronotope/chrono/issues/674

ben referenced this issue

2022-08-04 21:13:48 +02:00

add a link to reviewer notice mail and update dependencies #34

ben commented

2022-08-04 21:15:45 +02:00

Author

Owner

The chrono version being used is now update in main, now only a new release and its deployment is missing