chore!: upgrading forc to 0.55.0

[arboleya]

• Close Upgrade forc to 0.55.0 #2042

Breaking Changes

1) AssetId & EvmAddress

Property value was renamed to bits.

• Before:

  fuels-ts/packages/interfaces/src/index.ts

  Lines 23 to 35 in 498cffe

  	/**
  	* @prop value - A 256 bit hash string with the first 12 bytes cleared
  	*/
  	export type EvmAddress = {
  	value: B256AddressEvm;
  	};
  	/**
  	* @prop value - A wrapped 256 bit hash string
  	*/
  	export type AssetId = {
  	value: B256Address;
  	};

• After:

  fuels-ts/packages/interfaces/src/index.ts

  Lines 23 to 35 in 574e682

  	/**
  	* @prop bits - A 256 bit hash string with the first 12 bytes cleared
  	*/
  	export type EvmAddress = {
  	bits: B256AddressEvm;
  	};
  	/**
  	* @prop bits - A wrapped 256 bit hash string
  	*/
  	export type AssetId = {
  	bits: B256Address;
  	};

2) Vector

Method encapsulation.

• Before:

  fuels-ts/packages/fuel-gauge/test/fixtures/forc-projects/script-with-vector/src/main.sw

  Line 15 in 67f8002

  log(vector.buf.ptr);

• After:

  fuels-ts/packages/fuel-gauge/test/fixtures/forc-projects/script-with-vector/src/main.sw

  Line 15 in e26dc07

  log(vector.ptr());

[arboleya]

Should we wait until sway-libs is compatible with forc 0.52.x before merging this?

@maschad I'm afraid we can't do that. We are already on a tight schedule.

However, if I may guess where your question is coming from, I think @Dhaiwat10 suggested a temporary fix for it.

[maschad]

Should we wait until sway-libs is compatible with forc 0.52.x before merging this?

@maschad I'm afraid we can't do that. We are already on a tight schedule.

However, if I may guess where your question is coming from, I think @Dhaiwat10 suggested a temporary fix for it.

Thanks for the clarification. I created #2160 as a follow-up.

The base branch was changed.

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
79.34%(+0%)	69.3%(+0%)	77.38%(+0%)	79.49%(+0%)

Changed Files:

Coverage values did not change👌.