-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Upgrading time
crate to 0.3.35
#3189
Comments
As a temporary workaround, just pin the version of time = "=0.3.34" Sorry @wyatt-herkamp, I'm sure you have the best of intentions, but given the recent attack on |
I tried doing that. However, it was still erroring out. I completely understand. I am using this in a school project so it won't get near production. Also I deleted the comment. I plan to delete the REPO as soon as an official fix has been released. |
Hi, all our pipelines are failing by this issue, any estimated deadline? |
If anyone is still having the same issue, please upgrade your local The breaking change in |
The
time
crate released a new 0.3.35 version, and it introduced a few breaking changes, mainly in the module naming and re-export path. Resulting in compile error, if one depends on the latesttime
release.Full log: https://github.com/SeaQL/sea-query/actions/runs/8626694053/job/23645278046#step:4:452
The text was updated successfully, but these errors were encountered: