Skip to content

Releases: FuelLabs/fuels-rs

v0.66.9

15 Oct 06:57
d99edd0
Compare
Choose a tag to compare

Chores

v0.66.8

13 Oct 23:00
92dd2cc
Compare
Choose a tag to compare

Summary

In this release, we:

  • Updated fuel-core to 0.38.0

Features

Chores

v0.66.7

06 Oct 12:43
aced66c
Compare
Choose a tag to compare

Summary

In this release, we:
Loader and Regular executables now offer insight into the data section offset within.

Configurables can be shifted by a i64 offset.

Default estimation horizon bumped from 1 to 5.

Features

Chores

v0.66.6

06 Oct 01:18
d0a9f8a
Compare
Choose a tag to compare

Summary

In this release, we:

  • Implemented support for pre-uploading code for scripts and predicates via blobs.

Features

Chores

v0.66.5

22 Sep 21:40
c0eec1f
Compare
Choose a tag to compare

Chores

v0.66.4

06 Sep 14:25
bf51d50
Compare
Choose a tag to compare

Summary

In this release, we:

  • fixed loader contracts not working when being called through a proxy contract

Fixes

v0.66.3

04 Sep 21:17
c7f6806
Compare
Choose a tag to compare

Fixes

Chores

v0.66.2

20 Aug 18:32
fd3924b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.66.1...v0.66.2

v0.66.1

16 Aug 23:01
59617c3
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.66.0...v0.66.1

v0.66.0

09 Aug 23:30
93f515e
Compare
Choose a tag to compare

What's Changed

Breaking changes

  • SizedAsciiString no longer implements AsRef<[u8]>. To get the underlying bytes, you can turn it into a &str via the new AsRef<str> and call as_bytes() on the &str: sized_string.as_ref().as_bytes().
  • build_without_signatures is now achieved by setting the build strategy to BuildStrategy::NoSignatures on the transaction builder before calling build.
  • .simulate() now accepts an Execution argument, allowing for realistic or state-read-only simulations.
  • fee_checked_from_tx is removed from all transaction builders. The max fee can now be estimated using the new method estimate_max_fee, which considers the maximum fee estimation tolerance set on the builders.
  • The SDK previously performed transaction validity checks, including signature verification, before sending a transaction to the network. This was problematic since the checks also included signature verification, even when UTXO validation was turned off. To enable this feature and prevent future issues like failed validation checks due to version mismatches between the network and the SDK's upstream dependencies, we decided to remove the check. Since the SDK already abstracts building transactions for common cases (contract calls, transfers, etc.), validity issues are unlikely.
  • Contract::new is removed and replaced with Contract::regular.
  • Contract now accepts a generic argument denoting the type of contract (regular, loader, etc.)

New Contributors

Full Changelog: v0.65.1...v0.66.0