[rutefig]

Why

This crate requests zk-regex-apis from zkemail/zk-regex at branch = "main", and so does the relayer-utils revision it is locked to. zk-regex#92 removes that crate from main. The committed Cargo.lock keeps working, but any re-resolve would break.

What

• Pin relayer-utils to fcd5333, the revision already in Cargo.lock. Tracking its main would otherwise pull in a much newer, incompatible API on the next update.
• Add a [patch] that redirects every zk-regex-apis request, direct and transitive, to tag 2.1.0. That is commit 491a2dc, the one already locked. The double slash in the patch URL is deliberate, Cargo refuses a patch that points to the same source it replaces.

No resolved commit changes. The lockfile diff is two source strings, plus the lockfile format going from v3 to v4, which needs Cargo 1.78 or newer.

I used 2.1.0 instead of 2.1.3 on purpose, so the code being built stays byte-identical.

Verification

cargo metadata --locked resolves with a single zk-regex-apis entry. No build was run because no source changed.

Summary by CodeRabbit

• Chores
  • Updated dependency sources to use fixed, immutable revisions for more consistent builds.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 7d72bfe2-0f8f-4972-8b11-a23d5fe77d0e

📥 Commits

Reviewing files that changed from the base of the PR and between e72c9f0 and aa03b61.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Cargo manifest pins relayer-utils to a Git revision and redirects zk-regex-apis to the 2.1.0 tag.

Changes

Dependency source pinning

Layer / File(s)	Summary
Cargo dependency source updates Cargo.toml	relayer-utils now uses a fixed Git revision. A Cargo patch redirects zk-regex-apis to the 2.1.0 tag through an alternate Git URL.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to aa03b

The dependency sources are pinned to the intended resolved revisions, with no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: pinning relayer-utils and zk-regex-apis to immutable references.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rutefig/pin-zk-regex-2x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}