Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update alloy and revm dependencies #89

Closed
nategraf opened this issue Apr 26, 2024 · 1 comment · Fixed by #93
Closed

Update alloy and revm dependencies #89

nategraf opened this issue Apr 26, 2024 · 1 comment · Fixed by #93

Comments

@nategraf
Copy link
Contributor

I ran into an issue when trying to release 0.10 due to inconsistent versions of alloy and revm. It does not appear when the Cargo.lock file is in use, but will effect downstream users. I mitigated the issue on the release-0.10 branch in #85. Fixing it on main should be done by updating the dependencies.
@nategraf nategraf mentioned this issue May 9, 2024
Merged
@nategraf
Copy link
Contributor Author

#93 updates alloy. Need to update revm https://github.com/risc0/risc0-ethereum/pull/93/files#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542R39

nategraf added a commit that referenced this issue May 15, 2024
@nategraf @capossele
Use the main branch of the risc0 monorepo for development (#93)
5959f6c 
This changes all the references for packages from `risc0` in the
`Cargo.toml` files. During development, we want to stay up to date with
the `main` branch of `risc0`, and only switch to a stable release during
the release process. With `1.0` approaching very soon now, the rate of
breaking changes should slow significantly.

Resolves: #73
Resolves: #89

Co-authored-by: carlosgj94

---------

Co-authored-by: capossele <angelocapossele@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use the main branch of the risc0 monorepo for development risc0/risc0-ethereum
1 participant
@nategraf