Skip to content
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

Non-semver breaking change in v3.7.0 #662

Open
prestwich opened this issue Dec 1, 2024 · 10 comments
Open

Non-semver breaking change in v3.7.0 #662

prestwich opened this issue Dec 1, 2024 · 10 comments

Comments

@prestwich
Copy link

Unsure what it was exactly, but ruint no longer compiles on 3.7.0

CI output here:
https://github.com/recmo/uint/actions/runs/12097285631/job/33732497498?pr=407

@bkchr
Copy link
Member

bkchr commented Dec 1, 2024

Hey @prestwich, see #656 for the same discussion.

@prestwich
Copy link
Author

Please check the CI logs above. This issue is not due to the MSRV change, but due to some sort of bounds change on either an assoc type requirement or on a blanket impl

@prestwich
Copy link
Author

if you want to reproduce to assure yourself it's not MSRV related, you can compile on 1.80 as follows

cd ruint
cargo +1.80 update -p parity-scale-codec --precise 3.6.12 
cargo +1.80 c --features parity-scale-codec
cargo +1.80 update -p parity-scale-codec --precise 3.7.0
cargo +1.80 c --features parity-scale-codec

@bkchr
Copy link
Member

bkchr commented Dec 2, 2024

Ahh sorry!

This is again this: recmo/uint#313

We forgot to revert the following changes on master: #545 🙈

@jsdw we should revert these changes on master, yank and release 3.7.1. Could you do this? Then at some point we should finally tackle 4.0.0.. 🙈

@jsdw
Copy link
Contributor

jsdw commented Dec 2, 2024

I don't 100% follow the issue right now (just packing for flight etc so don't have time to look much): how about I yank 3.7.0 now and then can look to fix the rest and release 3.7.1 later?

@jsdw
Copy link
Contributor

jsdw commented Dec 2, 2024

Ah I see, some PR to revert stuff was on a release branch instead of on master, so just need to apply that to master and we're good right? Maybe I have time lemme see

@jsdw
Copy link
Contributor

jsdw commented Dec 2, 2024

Ok, I yanked 3.7.0 already and opened #663 which was my attempt at reverting said PRs on master and resolving the various conflicts, but I need to look over it in more detail to be confident it does the right thing. Need to get packing etc so I'll have a look later and we can release 3.7.1 when we're happy!

@StackOverflowExcept1on
Copy link
Contributor

@jsdw can you also yank scale-codec-derive plz? it failed our CI: https://github.com/gear-tech/gear/actions/runs/12124067535/job/33800965532?pr=4340#step:14:1197
Cargo.lock contains 3.7.0 codec-derive and 3.6.12 codec
image

@jsdw
Copy link
Contributor

jsdw commented Dec 2, 2024

Apologies; been travelling. That is yanked too now!

@prestwich
Copy link
Author

thanks for this. I would like to support the breaking change in ruint when 4.0.0 releases. In the meantime I'm going to close this as stale: recmo/uint#313 and link back to this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants