Repository navigation
ci: pause crates.io publishing and release assets - #424
Conversation
The OP crates are pinned to a git revision and cargo publish rejects git dependencies, so the crates job in the release workflow could only fail. The job is removed, and the install docs now point at release tags.
Releases are immutable once published and this workflow runs after publishing, so uploading the binary to the Release fails with HTTP 422. The upload step and the prebuilt-binary docs are removed, and the binary still goes to the artifact registry.
Claude review status
✅ Review clean Last reviewed: New this round: 0 finding(s), 0 question(s) · Resolved this round: 0 · Open questions: 0 |
🧬 Mutation testingNo results at |
🧬 Spec-gate mutation — ✅ PASSNothing to test — no mutants were generated on the changed lines. |
Merging this PR will not alter performance1 warning
Comparing Footnotes
|
The README install instructions now give the plain cargo install command from the GitHub repository, without a hand-filled tag.
The Installation section now lists installing from GitHub and from a Git checkout as two plain alternatives.
Sync the mega-evme overview install section and tighten wording in the release workflow, README and release skill.
Summary
Two publish targets in
on-release.ymlfail on every release now: thecratesjob and therelease-assetsstep. v1.7.3 hit both. This PR removes them and updates the docs that promised their results.crates.io publishing is paused.
op-revm,alloy-op-evm,alloy-op-hardforks,op-alloy-consensus,op-alloy-networkandop-alloy-rpc-types.cargo publishrejects git dependencies. See the note in the rootCargo.toml.cratesjob. To resume once those crates are on crates.io, restore it from this PR.README.md,bin/mega-evme/README.mdanddocs/mega-evme/overview.mdnow document two ways to installmega-evme, and note that building requires Foundry'sforge:cargo install --git https://github.com/megaeth-labs/mega-evm --locked mega-evme;git clone --recursive …, thencargo install --locked --path bin/mega-evme.Release assets are paused.
on-release.ymlruns onrelease: published, sorelease-assetsfails withHTTP 422: Cannot upload assets to an immutable release. v1.7.3 has no assets for this reason, and stateless-validator v2.1.0 failed the same way.release-assetsstep, together with thecontents: writepermission on themega-evmejob. It also removes the "Prebuilt binary" sections fromREADME.md,bin/mega-evme/README.mdanddocs/mega-evme/overview.md.REVIEW.mdand thebump-version-releaseskill are updated to match.Test plan
mega-evmejob is unchanged except for the removedrelease-assetsstep and itscontents: writepermission. Checked by comparing the parsed workflow withmain, plusactionlintandapp-token-lint.mega-evme 1.7.3:cargo install --git https://github.com/megaeth-labs/mega-evm --locked mega-evme;git clone --recursive https://github.com/megaeth-labs/mega-evm, thencargo install --locked --path bin/mega-evme.CARGO_REGISTRY_TOKEN,release-assets,SHA256SUMSor a prebuilt download outsideCHANGELOG.md.on-releaserun passes, with the artifact registry upload only.Labels checklist
spec:unchangedcomp:miscapi:unchanged