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.

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

Update to 0.21 #89

Merged
merged 22 commits into from
Mar 21, 2024
Merged

Update to 0.21 #89

merged 22 commits into from
Mar 21, 2024

Conversation

capossele
Copy link
Contributor

@capossele capossele commented Mar 11, 2024

@capossele capossele self-assigned this Mar 11, 2024
@capossele capossele changed the title Update to 0.21.0-rc2 Update to 0.21 Mar 14, 2024
Comment on lines 40 to 50
- name: Install cargo-install
uses: risc0/cargo-install@v1
with:
crate: cargo-binstall

- name: Cargo binstall cargo-risczero
run: cargo binstall -y --force cargo-risczero@${{ env.RISC0_CRATE_VERSION }}
- name: Cargo install cargo-risczero
run: cargo install --force --locked cargo-risczero@$RISC0_CRATE_VERSION
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC, this will take quite a bit longer than installing and using binstall because it'll require building the prover, which is quite slow at the moment. Is there a particular reason to do it this way instead?

Comment on lines 69 to 70
- run: sccache --show-stats

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think sccache is installed/initialized in this workflow right now. My thought on not including it is that we expect folks to clone/fork this repo and the likely host their code on GitHub. When they do, we'd like it to be simple for them to enable GitHub actions based CI. In that flow, sccache adds some friction as we've had to do quite a bit of work to get it running smoothly (but maybe I am overstating how much friction we've experienced)

Suggested change
- run: sccache --show-stats

Comment on lines 84 to 95
- name: Install cargo-install
uses: risc0/cargo-install@v1
with:
crate: cargo-binstall

- name: Cargo binstall cargo-risczero
run: cargo binstall -y --force cargo-risczero@${{ env.RISC0_CRATE_VERSION }}
- name: Cargo install cargo-risczero
run: cargo install --force --locked cargo-risczero@$RISC0_CRATE_VERSION
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above

Cargo.toml Outdated
@@ -12,19 +12,17 @@ alloy-primitives = { version = "0.6", default-features = false, features = ["rlp
alloy-sol-types = { version = "0.6" }
anyhow = { version = "1.0.75" }
bincode = { version = "1.3" }
bonsai-sdk = { version = "0.6.1" }
bonsai-sdk = { git = "https://github.com/risc0/risc0", branch = "release-0.21" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be a version ref, matching the one in risc0-ethereum?

@capossele capossele marked this pull request as ready for review March 21, 2024 19:52
Copy link
Contributor

@mothran mothran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@capossele capossele merged commit af0e887 into main Mar 21, 2024
3 checks passed
@capossele capossele deleted the capossele/risc0-CI branch March 21, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants