fix(ci): cut run-integration-test.yml over to "mlugg/setup-zig@v2", clippy fixes #1005
+20
−21
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.
✍️ Description of changes:
Run-integ setup-zig action change
We had pinned back our
cargo-lambda
version due to CI failures. Ref: #989The
cargo-lambda
issue was closed because it was determined that the issue had to do with the underlying zig install. essentially, you need libraries available, not just the binary. Ref: cargo-lambda/cargo-lambda#856 (comment)In the process of cleaning up, I noticed we were using an archived action. Cutting us over to the modern one.
Unfortunately, this wasn't sufficient to fix the issue, sample run, so leaving us pinned for now. I cut a backlog: #1006
Clippy fixes
The new clippy turned inline variable enforcement in fmt strings from
pedantic
towarn
, so our CI started failing. Fixing.🔏 By submitting this pull request
cargo +nightly fmt
.cargo clippy --fix
.