v0.66.0

What's Changed

• chore: update forc build path in docs by @danielbate in #1459
• feat!: unfunded read only calls by @segfault-magnet in #1412
• bug!: accounts now cover max fee increase due to tolerance by @segfault-magnet in #1464
• chore: use forc 0.62.0 by @hal3e in #1466
• docs: Fix callParams broken link by @calldelegation in #1461
• chore: bump rust to 1.79.0 by @Br1ght0ne in #1467
• ci: bump (and pin) rust-cache action to v2.7.3 by @Br1ght0ne in #1468
• feat!: implement abi spec changes by @esdrubal in #1465
• feat!: account impersonation by @MujkicA in #1473
• feat: remove legacy code for abi without callpaths by @hal3e in #1474
• chore: enable testnet connection test by @hal3e in #1476
• feat!: deploying large contracts (loader + blob support) by @segfault-magnet in #1472
• chore: bump versions to 0.66.0 by @digorithm in #1478

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

• @danielbate made their first contribution in #1459
• @calldelegation made their first contribution in #1461
• @esdrubal made their first contribution in #1465

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