fix(ci/cd): pin cargo-lambda back to 1.8.1 temporarily #989
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📬 Issue #, if available:
n/a
✍️ Description of changes:
Fix for:
https://github.com/awslabs/aws-lambda-rust-runtime/actions/runs/14909766508/job/41880956336#step:7:36
This is a known regression in
cargo-lambda
: cargo-lambda/cargo-lambda#856Pinning back until it is fixed upstream.
🔏 By submitting this pull request
cargo +nightly fmt
.cargo clippy --fix
.