feat: update CI release workflow#49
Conversation
jsign
left a comment
There was a problem hiding this comment.
LGTM.
Agree, at some point might be good to remove the empty and panic guest programs. Maybe the panic one might be useful, but it feels to me that the case should be more like a separate interesting use-case for zkVM standards repo (or adjacent repo) than ere-guests, maybe.
Mainly, if removing them could simplify the ere-guests architecture further.
Make sense, actually the panic guests are tested in |
Remove publishing
emptyandpanicELFs (guests kept to do testing for now, but I think we'd remove them eventually)Add build script to populate
EL_VERSIONforstateless-validator-ethrexandstateless-validator-rethGenerate release note by python script in a table format (resolves Displaying target information #22), a sample:
release-body.mdCompiled guest programs
Built with Ere compiler version:
v0.12.0.ethrexb112f94risc0v3.0.5riscv32imethrexb112f94sp1v6.1.0riscv32imethrexb112f94ziskv0.18.0riscv64imrethv2.1.0airbender73d69b5riscv32imrethv2.1.0openvmv1.4.3riscv32imrethv2.1.0risc0v3.0.5riscv32imrethv2.1.0sp1v6.1.0riscv32imrethv2.1.0ziskv0.18.0riscv64imAdd a
artifact-registry.jsonso we can maintiain the ELF republish metadata in it in the future, and CI and the release body generation script will use it to do republishment, a sample:artifact-registry.json{ "stateless-validator-elf": { "{el}-{zkvm}": { "url": "https://stateless-validator-{el}-{zkvm}.elf", "el_version": "vX.Y.Z", "zkvm_version": "vX.Y.Z" } }, "stateless-validator-static-library": { "{el}": { "url": "https://stateless-validator-{el}.a", "version": "vX.Y.Z" } }, "zkvm-static-library": { "{zkvm}": { "url": "https://{zkvm}.a", "version": "vX.Y.Z" } } }