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

Upgrade to 2024 edition with minor version release breaks downstream dependencies #1687

Closed
bhavink09 opened this issue Feb 26, 2025 · 1 comment

Comments

@bhavink09
Copy link

Our project links to base64ct via transitive dependency which does not lock the exact version of base64ct. Given the edition2024 upgrade was a minor release, this gets automatically picked up and forces all projects to be upgraded to edition2024, which is not what we intend to do atm.

Is there a way to revert this in minor version and release a major version for it? Or any other way to resolve it downstream please?

@tarcieri
Copy link
Member

Dup of #1684

I'll also note that previous releases of base64ct explicitly stated the following as our SemVer policy for MSRV

We may change the MSRV in the future, but it will be accompanied by a minor version bump.

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

2 participants