Update dependencies to allow building with latest Rust version

[BigBadE]

Rust changing features broke proc, which broke any crates or dependencies using it. This PR simply updates to the latest version of each dependency to fix this issue.

Changes:

• Swapped to bincode 2.0.0, switching encode/decode methods to their 2.0.0 serde equivalent
• Fixed tests to use modern rust assert_eq and its variants
• swapped u32::max_value() to the modern u32::MAX suggested equivalent

I ran all tests, no errors.

[cecton]

That is awesome thanks a lot! Can you fix the remaining issue? The CI must be green I can't just leave a ❎ like that

[cecton]

I wonder if this shouldn't be upgraded now. Can you check the different versions to see which ones work?

[BigBadE]

Why do you think it shouldn't be upgraded?

[cecton]

No I meant the opposite. Should this be upgraded too, to 0.6 or up idk

[BigBadE]

There is no 0.6, 0.5.1 is the latest (https://docs.rs/serde-big-array/latest/serde_big_array/).

[BigBadE]

There we go, clippy warnings fixed

[BigBadE]

Ah, so that's why. Up to @cecton whether to bump the MSRV or to go back down to a 1.x bincode version, which I assume would work on the latest Rust still.

[cecton]

Ah, so that's why. Up to @cecton whether to bump the MSRV or to go back down to a 1.x bincode version, which I assume would work on the latest Rust still.

Yes I guess since bincode 2 is still just a release candidate, we can't really make a stable release of mbrman like that. Once they finally release it then we can

[BigBadE]

It seems fine for a stable release, given it's just legacy bincode 1 code, it would just require upping the MSRV to match bincode 2's MSRV

[guenhter]

Any update on this?

[cecton]

It looks abandoned. If you want you can make a new PR, fix the CI and I will merge and release.

[BigBadE]

I never got a decision on whether I should bump the MSRV or go back down to bincode 1.x, unless "yes" meant to downgrade.

[cecton]

oh sorry I remember now I thought it was clear. We can't make a stable release here with a dependency on a release candidate. So using bincode 2 is not acceptable at the moment.

But without the upgrade to bincode 2 I assume it won't solve the issue? In that case this PR needs to stay dormant until bincode 2 finally release its stable version.

[cecton]

For anyone who absolutely need this upgrade: you can add a [patch] section in your cargo to use @BigBadE repo and branch with the upgrade. If you find any issue you can report them in this ticket here.

[cecton]

bincode has been released in stable on March 6th 2025. I updated the dependencies and merged