ci: add shear, workspace inheritance, and zizmor checks, and move heavy GitHub Actions jobs to WarpBuild#2013
Conversation
| Err(err) => return Err(err), | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
Just wondering if 30 attempts with 200ms is what we want here.
sergerad
left a comment
There was a problem hiding this comment.
LGTM just wondering about the retry logic added, commented inline.
sergerad
left a comment
There was a problem hiding this comment.
Ran the Debian workflows which seemed to fail. Created a v0.0.0-test.1 tag for this branch's latest commit.
|
@sergerad Indeed, one fix was needed in this branch: tag refs must be peeled to commits before using them with |
I updated the tag to your latest commit but still failing https://github.com/0xMiden/node/actions/runs/25145113300 |
02eb99c to
0cba4e5
Compare
0cba4e5 to
f50b158
Compare
|
@sergerad Docker-tested and passing on my side. |
sergerad
left a comment
There was a problem hiding this comment.
LGTM TY.
Debian release worked until the point of where the Github release is expected to exist 👍
https://github.com/0xMiden/node/actions/runs/25192465857
This adds three CI checks for repo health.
cargo-shearchecks for unused or misplaced Rust dependencies.zizmorchecks GitHub Actions files for unsafe patterns.cargo-workspace-inheritance-checkmakes shared dependencies use one workspace entry.Heavy Rust jobs now run on WarpBuild runners to reduce CI time (tests: 18m -> 8m). The PR also pins Actions more tightly, removes unused dependencies found by cargo-shear, and keeps workspace dependency versions centralized.