Patch/ci 510 fixups - #536
Open
Cedarich wants to merge 5 commits into
Open
Conversation
Ensure soroban/events.json and soroban/events.txt are on their own lines so they are actually ignored.
Ensure Makefile command lines use real tabs and add a fmt-check target that runs `cargo fmt --all -- --check`.
- Add cargo-llvm-cov coverage reporting and upload artifact - Make cargo-audit actionable (fail on high/critical advisories) - Make WASM size warn >100KB and fail >150KB - Keep toolchain pinned to stable with toolchain 1.91.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Provide a clear summary of what this PR changes and why.
Related Issue(s)
Link any related issue(s) using
#<issue-number>.If this PR closes an issue, include
Closes #<issue-number>.Type of Change
Description
Describe the implementation details and scope of the changes.
Testing Evidence
Describe how this change was tested, including commands run or test cases executed.
Include links to test outputs, screenshots, or any relevant evidence.
Screenshots
Add screenshots, GIFs, or recordings when UI or visual behavior changed.
Checklist