Skip to content

[MSRV] Document policy for when/how MSRV will roll forward #986

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

Open
jlizen opened this issue May 6, 2025 · 0 comments
Open

[MSRV] Document policy for when/how MSRV will roll forward #986

jlizen opened this issue May 6, 2025 · 0 comments

Comments

@jlizen
Copy link
Contributor

jlizen commented May 6, 2025

Our current MSRV policy is in the README:
https://github.com/awslabs/aws-lambda-rust-runtime/blob/main/README.md#supported-rust-versions-msrv

The AWS Lambda Rust Runtime requires a minimum of Rust 1.81.0, and is not guaranteed to build on compiler versions earlier than that.

Presumably someday we will want to roll it forward. Projects often say something like, 'we will support a minimum of the last 6 months of rust versions, and will only roll forward if we need a new feature'. It would be nice to clarify that.

We probably should also explicitly state whether a MSRV bump is considered a breaking semver change or no.

At some point in the future, when we are rolling forward MSRV and guaranteeing support for both new and old for a period of time, we probably also want to add some github actions to test against multiple rust 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

No branches or pull requests

1 participant