Skip to content

Conversation

Thomasdezeeuw
Copy link

No description provided.

@Thomasdezeeuw
Copy link
Author

We bumped the MSRV to 1.70 in socket2 v0.6, I'll let it up to the maintainers to decide if that's ok to bump.

@seanmonstar
Copy link
Member

While our policy allows for upgrading, I try pretty hard to support 1.63 for Debian.

@Thomasdezeeuw
Copy link
Author

While our policy allows for upgrading, I try pretty hard to support 1.63 for Debian.

That's a totally fair decision.

Note that Mio, dependency of Tokio, also uses Rust 1.70 already as of Tokio 1.39 (CI seems to use v1.38.1).

@seanmonstar
Copy link
Member

Yea if I can pin a dependency for CI, I find that valid: users can choose to pin as well, or use a newer version, they get the choice.

@tottoto
Copy link
Contributor

tottoto commented Jul 7, 2025

Since the test CI is successful with just the version update, it seems that the current usage is not affected by the breaking change. If that is the case, it might be possible to keep the MSRV by allowing both 0.5.9 and 0.6 versions.

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

Successfully merging this pull request may close these issues.

3 participants