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

chore(bindings): Pin zeroize to avoid MSRV increase #4519

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

goatgoose
Copy link
Contributor

@goatgoose goatgoose commented Apr 24, 2024

Description of changes:

The zeroize crate has updated their MSRV to 1.72 which causes the rust bindings build to fail, see #4518. This PR pins zeroize to the previous version in order to avoid the MSRV increase.

Testing:

The CI should build the rust bindings successfully.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions github-actions bot added the s2n-core team label Apr 24, 2024
@goatgoose goatgoose marked this pull request as ready for review April 24, 2024 21:59
@@ -45,3 +45,4 @@ cc = { version = "1.0", features = ["parallel"] }
jobserver = "=0.1.26" # newer versions require rust 1.66, see https://github.com/aws/s2n-tls/issues/4241
home = "=0.5.5" # newer versions require rust 1.70, see https://github.com/aws/s2n-tls/issues/4395
regex = "=1.9.6" # newer versions require rust 1.65, see https://github.com/aws/s2n-tls/issues/4242
zeroize = "=1.7.0" # newer versions require rust 1.72, see https://github.com/aws/s2n-tls/issues/4518
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: This isn't really a PR issue, but maybe it would make sense to have a single tracking issue with the pins rather than making a new pin for each one? And just keep the list sorted by "required MSRV"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that makes sense. I will merge this first though to unblock the CI. #4521

@goatgoose goatgoose enabled auto-merge (squash) April 24, 2024 22:38
@goatgoose goatgoose merged commit e2bd4ee into aws:main Apr 24, 2024
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants