Release v0.27.0

[xgreenx]

Version v0.27.0

Added

• #1898: Enforce increasing of the Executor::VERSION on each release.

Changed

• #1906: Makes cli::snapshot::Command members public such that clients can create and execute snapshot commands programmatically. This enables snapshot execution in external programs, such as the regenesis test suite.
• #1891: Regenesis now preserves FuelBlockMerkleData and FuelBlockMerkleMetadata in the off-chain table. These tables are checked when querying message proofs.
• #1886: Use ref to Block in validation code
• #1876: Updated benchmark to include the worst scenario for CROO opcode. Also include consensus parameters in bench output.
• #1879: Return the old behaviour for the discovery_works test.
• #1848: Added version field to the Block and BlockHeader GraphQL entities. Added corresponding version field to the Block and BlockHeader client types in fuel-core-client.
• #1873: Separate dry runs from block production in executor code, remove ExecutionKind and ExecutionType, remove thread_block_transaction concept, remove PartialBlockComponent type, refactor away inner functions.
• #1900: Update the root README as fuel-core run no longer has --chain as an option. It has been replaced by --snapshot.

Breaking

• #1894: Use testnet configuration for local testnet.
• #1894: Removed support for helm chart.
• #1910: fuel-vm upgraded to 0.50.0. More information in the changelog.

What's Changed

• feat: Support block and header versions gql by @bvrooman in feat: Support block and header versions gql #1848
• Updated croo opcode benchmark to depend on the contract size by @xgreenx in Updated croo opcode benchmark to depend on the contract size #1876
• Return the old behaviour for the discovery_works test by @xgreenx in Return the old behaviour for the discovery_works test #1879
• Weekly cargo update by @github-actions in Weekly cargo update #1880
• Separate production from dry runs in executor & Cleanup all execution paths :) by @MitchTurner in Separate production from dry runs in executor & Cleanup all execution paths :) #1873
• Use ref instead of owned Block in validation by @MitchTurner in Use ref instead of owned Block in validation #1886
• Weekly cargo update by @github-actions in Weekly cargo update #1893
• ci: fix typos programmatically by @sdankel in ci: fix typos programmatically #1890
• feat: Preserve message proofs post-regenesis by @bvrooman in feat: Preserve message proofs post-regenesis #1891
• chore: update README fuel-core run options by @K1-R1 in chore: update README fuel-core run options #1900
• Weekly cargo update by @github-actions in Weekly cargo update #1903
• chore: Make snapshot command members pub accessible by @bvrooman in chore: Make snapshot command members pub accessible #1906
• Use testnet configuration for local testnet by @xgreenx in Use testnet configuration for local testnet #1894
• Enforce increasing of the Executor::VERSION on each release by @xgreenx in Enforce increasing of the Executor::VERSION on each release #1898
• Bumped the version of the fuel-vm to 0.50.0 by @xgreenx in Bumped the version of the fuel-vm to 0.50.0 #1910

New Contributors

• @K1-R1 made their first contribution in chore: update README fuel-core run options #1900

Full Changelog: v0.26.0...v0.27.0

[MitchTurner]

Just one little question, but not blocking. LGTM.

[MitchTurner]

Did we just not need this before? It seems like the wasm_executor_path is the "offline" path. Is that right?

[xgreenx]

It was not needed, I just tried to cover all the cases of how this crate could be used. I assumed that because we will build fuel-core-wasm-executor as a dependency, it would pull all required crates. But it is not true because dependency may have different(bumped) dependencies, while to build a WASM bytecode, we are using --locked.

[MitchTurner]

Oh. Looks like you need to bump another location, maybe?