patching-dependencies

You can patch Cargo workspace dependencies to local checkouts by using Diener to modify Cargo.toml, redirecting crates from multiple repositories to your local file paths for coordinated multi-repo testing.

Testing cross-repo feature development across polkadot-sdk and frontier is done by patching workspace dependencies to local checkouts or alternate branches, allowing you to verify changes across repositories without pushing upstream.

Yes, Diener is required to patch Moonbeam-related crates across polkadot-sdk, frontier, and moonkit, as it handles the Cargo.toml modifications needed to redirect dependencies to your local checkouts.

To revert patched dependencies and restore original references, you use the patching tool's revert functionality, which removes local checkout redirects and resumes standard CI and build flows.

After patching dependencies to a local branch, a cargo build may fail if dependency versions are misaligned; running cargo update after patching Cargo.toml helps synchronize and verify the changes.

Yes, you can update workspace dependencies to a specific branch, tag, or commit across multiple repositories by patching them to point to alternate references, enabling coordinated testing without upstream pushes.