ethereum-optimism / ethereum-optimism/optimism
fix(rust): adapt rust stack release process to the monorepo
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
## Description
Following the migration of the rust stack crates to the monorepo, we need to start adding support for rust stack releases in our CI.
- [ ] `kona` (`kona-node`, `kona-host`, `kona-client`)
- [ ] `op-alloy`
- [ ] `alloy-op-evm`
- [ ] `alloy-op-hardforks`
- [ ] `op-revm`
- [ ] `op-reth`
Contributor guide
Research direction
Start by locating the existing release process in the repository's CI configuration and reviewing how non-Rust stacks are released after the monorepo migration. Trace the release path for the listed crates—kona, op-alloy, alloy-op-evm, alloy-op-hardforks, op-revm, and op-reth—and consider the work complete when CI supports releases for each one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100