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

refactor(prover): Switch prover workspace to workspace deps #1490

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

popzxc
Copy link
Member

@popzxc popzxc commented Mar 25, 2024

What ❔

Prover follow-up to #1485

Why ❔

Same reasons

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zk fmt and zk lint.
  • Spellcheck has been run via zk spellcheck.
  • Linkcheck has been run via zk linkcheck.

@popzxc popzxc marked this pull request as ready for review March 25, 2024 09:47
@popzxc popzxc requested a review from EmilLuta March 25, 2024 09:48
Copy link
Contributor

@EmilLuta EmilLuta left a comment

Choose a reason for hiding this comment

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

I'm super excited with these changes. Thanks for going through! There are a bunch of "unpinned" crates that make me feel uneasy (circuit_definitions, shivini, zkevm_test_harness/1_3_3). I know from crypto side that commits might be pushed on top of the branch, which would result in us potentially running code we're not intending. Any thoughts on that? (Yeah, the .lock should protect us from that, but an update to the .lock for a dependency might have nefarious updates bundled in)

prover/Cargo.toml Show resolved Hide resolved
@popzxc popzxc added this pull request to the merge queue Mar 25, 2024
Merged via the queue into main with commit d593c1b Mar 25, 2024
27 checks passed
@popzxc popzxc deleted the popzxc-prover-workspace-deps branch March 25, 2024 11:49
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.

2 participants