This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
Temporarily fix cairo-lang dependency version issues after major upgrades #995
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I was merging changes on my other PR, I noticed some issues when
starknet
was being executed on the workflow tests, and they didn't seem to have been caused by my changes.Turns out that the errors were related to breaking changes from two
cairo-lang
dependencies that were upgraded to the next major version literally like 3 days ago, more specificallyweb3
andtypeguard
. Sincecairo-lang
didn't have a specific major version matching, it accepted the new package versions while not yet supporting them, and then these errors happened. There's already an open issue for this: starkware-libs/cairo-lang#151.In the latest
cairo-lang
pre-release,typeguard
is already set to<3.0.0
, butweb3
isn't yet. When both of these are fixed and there's a new release, it would be good to upgrade it here. For the moment, I added explicit installs forweb3
(==5.*
) andtypeguard
(==2.*
), which seem to have done the trick.