feat(release/rust): set up release process for rust crates#19155
Merged
feat(release/rust): set up release process for rust crates#19155
Conversation
Contributor
Plan expiredYour subscription has expired. Please renew your subscription to continue using CI/CD integration and other features. |
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #19155 +/- ##
===========================================
+ Coverage 73.5% 75.6% +2.0%
===========================================
Files 188 504 +316
Lines 10946 60591 +49645
===========================================
+ Hits 8055 45829 +37774
- Misses 2745 14762 +12017
+ Partials 146 0 -146
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
theochap
force-pushed
the
theo/rust-release
branch
from
0cb5201 to
3d2e854
Compare
sebastianst
reviewed
Feb 12, 2026
Member
sebastianst
left a comment
sebastianst
left a comment
There was a problem hiding this comment.
This does not set up releases of crates to crates.io, right?
Member
Author
Yes, this is what we talked about with george yesterday |
theochap
force-pushed
the
theo/rust-release
branch
2 times, most recently
from
1fa1eaa to
0a18520
Compare
sebastianst
approved these changes
Feb 13, 2026
- Add tag classification to distinguish Rust crate groups from Docker-only groups - Add publish-crates CI job for crates.io publishing with dependency-ordered releases - Add op-reth Docker bake target and compute-git-versions entry - Add cargo-release configuration for alloy-op-hardforks and op-reth - Add .dockerignore for rust/ build context - Fix op-reth DockerfileOp manifest paths
theochap
force-pushed
the
theo/rust-release
branch
from
0a18520 to
8f0bf51
Compare
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
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
2 participants
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
tags.yamlworkflow to distinguish Rust crate groups (publish to crates.io) from Docker-only groups (op-reth) and regular Go imagespublish-cratesCI job that publishes crates in dependency order with retry logic and index propagation delays.dockerignore, andcompute-git-versionsentrycargo-releaseconfiguration foralloy-op-hardforksandop-rethDockerfileOpmanifest paths (crates/optimism/bin->op-reth/bin)Test plan
alloy-op-hardforks/v*triggerspublish-cratesonly,op-reth/v*triggersrelease(Docker) only,op-node/v*triggersreleaseonlypublish-rust-crates.shlocally for each group to verify crate orderingdocker buildx bake op-reth🤖 Generated with Claude Code