Skip to content

WEB3-513: contracts: dependency cleanups#654

Draft
Wollac wants to merge 5 commits into
mainfrom
wollac/contracts-alloy
Draft

WEB3-513: contracts: dependency cleanups#654
Wollac wants to merge 5 commits into
mainfrom
wollac/contracts-alloy

Conversation

@Wollac

@Wollac Wollac commented Jul 29, 2025

Copy link
Copy Markdown
Contributor
  • Hide SetVerifierService behind feature
  • Use alloy-provided decode error functionality
  • alloy has been released in v1, so there is no immediate need anymore to expose it

@Wollac Wollac requested a review from a team as a code owner July 29, 2025 11:35
@github-actions github-actions Bot changed the title contracts: dependency cleanups WEB3-513: contracts: dependency cleanups Jul 29, 2025

@nategraf nategraf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good overall. Thank you for working taking care of this.

Comment thread contracts/src/lib.rs
Comment on lines -20 to -25
/// Re-export of [alloy], provided to ensure that the correct version of the types used in the
/// public API are available in case multiple versions of [alloy] are in use.
///
/// Because [alloy] is a v0.x crate, it is not covered under the semver policy of this crate.
pub use alloy;

Copy link
Copy Markdown
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 we should remove this, because it might break downstream users and I think this is actually still helpful.

nategraf
nategraf previously approved these changes Aug 5, 2025
@nategraf nategraf requested review from a team as code owners October 3, 2025 18:23
@nategraf nategraf marked this pull request as draft October 3, 2025 20:37
@nategraf

nategraf commented Oct 3, 2025

Copy link
Copy Markdown
Contributor

I like the idea of bringing in alloy only if needed. As it stands, this will be a breaking change including in code that is not marked with unstable. I'll take this PR over and bring it in with the next major version bump.

@nategraf nategraf self-requested a review October 3, 2025 20:38
@nategraf nategraf dismissed their stale review October 3, 2025 20:39

Updated my understanding

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