Update Cargo.lock, pin time dependecy

[andrei-21]

The newer time version requires Rust 1.88

[ldk-reviews-bot]

👋 Thanks for assigning @tankyleo as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tankyleo]

The MSRV bump happened in 0.3.46 so let's set this to 0.3.45

[andrei-21]

Done

[tankyleo]

Thanks for the PR !

Do I understand correctly, on the current main branch, cargo +1.85.0 build succeeds on your local machine, but fails in your docker setup ?

You need to build with --locked in CI.

Because you want CI to enforce that builds pass for the exact Cargo.lock version checked in? Yes I agree. But the reason cargo build --locked fails on the current main branch is not due to the time MSRV bump, and I want to make sure we agree here.

[andrei-21]

Do I understand correctly, on the current main branch, cargo +1.85.0 build succeeds on your local machine, but fails in your docker setup ?

With this change it works locally and in docker.

Because you want CI to enforce that builds pass for the exact Cargo.lock version checked in? Yes I agree. But the reason cargo build --locked fails on the current main branch is not due to the time MSRV bump, and I want to make sure we agree here.

Correct.

[tankyleo]

Thanks @andrei-21 can you run cargo update again ? When I run this command on top of your branch, I get a pretty big update to the Cargo.lock. Then as before we pin the time dependency.

[tankyleo]

Also fix the typo in the commit message thank you :)

[tankyleo]

Thank you Andrei !

[tnull]

Might want to follow-up, see #92