fix: point std to local version for forc-client cli tests #5457
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kayagokalp
added
testing
Merged
kayagokalp
force-pushed
the
kayagokalp/fix-forc-client-tests
branch
from
a7ad1bf to
14bab17
Compare
ironcev
approved these changes
Jan 12, 2024
crodas
approved these changes
Jan 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
It seems like we accidentally depend on released version of std in forc-client deployment cli tests (more specifically the test folder https://github.com/FuelLabs/sway/tree/master/forc-plugins/forc-client/tests). This PR fixes it to point local version of std so that release PRs such as #5452 won't get blocked.