Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore!: upgrade forc to 0.56.0 #2180

Merged
merged 19 commits into from
Apr 26, 2024
Merged

Conversation

arboleya
Copy link
Member

@arboleya arboleya commented Apr 26, 2024


  1. Stop using --experimental-new-encoding flag — sway/pull/5915
  2. Fixed outdated implementations — check sway's breaking changes
  3. Fixed dead links and point them to new documentation URLs — check related PR docs-hub/pull/249

@petertonysmith94

This comment was marked as resolved.

@arboleya arboleya marked this pull request as draft April 26, 2024 12:39
@arboleya

This comment was marked as resolved.

@arboleya arboleya changed the title chore: upgrade forc to 0.56.0 chore!: upgrade forc to 0.56.0 Apr 26, 2024
@arboleya arboleya marked this pull request as ready for review April 26, 2024 15:40
@arboleya arboleya requested a review from nedsalk April 26, 2024 15:51
@fuel-service-user
Copy link
Contributor

fuel-service-user commented Apr 26, 2024

✨ A PR has been created under the rc-2180 tag on fuels-wallet repo.
FuelLabs/fuels-wallet#1256

nedsalk
nedsalk previously approved these changes Apr 26, 2024
Copy link
Contributor

Coverage Report:

Lines Branches Functions Statements
79.07%(+0%) 68.92%(+0%) 77.11%(+0%) 79.19%(+0%)
Changed Files:

Coverage values did not change👌.

@arboleya arboleya requested a review from nedsalk April 26, 2024 16:41
@arboleya arboleya merged commit 29f46ef into master Apr 26, 2024
25 of 27 checks passed
@arboleya arboleya deleted the aa/chore/upgrade-to-forc-0.56.0 branch April 26, 2024 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Issue is a chore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade forc to 0.56.0
5 participants