Skip to content

Conversation

@hiletmis
Copy link

Closes #2031

@hiletmis hiletmis changed the title Migrate to api3 contracts Migrate to @api3/contracts Aug 25, 2025
@hiletmis hiletmis added the blocked Blocked by another issue/PR label Aug 25, 2025
@dcroote
Copy link
Contributor

dcroote commented Aug 25, 2025

Disregard the failing docker build CI- this is expected until there is a changeset merged to the master branch. This happens when there aren't yet changessets after a release (which is true now because this would be the first commit since v0.15). (#1585)

@hiletmis
Copy link
Author

Thanks for the notice @dcroote.I had to add --ignore-engines to check if there is an additional problem to strict engines rule. Because @api3/contracts requires node to be >=20.17.9 for now and yet it will be >=22.18.0 on next release.

@hiletmis hiletmis requested review from Siegrift and dcroote November 13, 2025 08:31
@hiletmis hiletmis marked this pull request as ready for review November 13, 2025 08:31
@hiletmis hiletmis removed the blocked Blocked by another issue/PR label Nov 13, 2025
@Siegrift Siegrift removed their request for review December 1, 2025 13:11
@Siegrift
Copy link
Contributor

Siegrift commented Dec 1, 2025

I leave this to @dcroote

@dcroote
Copy link
Contributor

dcroote commented Dec 2, 2025

Addressing the e2e CI failure in #2041

@hiletmis
Copy link
Author

hiletmis commented Dec 5, 2025

contracts package is not bumped anyway. Is there any specific reason not to use integrated hardhat-config and abandon @api3/contracts package

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.

Use @api3/contracts instead of @api3/chains

4 participants