Release 3.0.0
3.0.0 - 2025-04-04
Fixed
- Inconsistent data path due the snap packages
- Remove deprecated help description files and use direct descriptors
- ReadTheDocs build with uv
- Untracked permissions for executable file in the git repository
- Remove non-output prints
- use blake2b for wasm code hash
- missing code hash update when upgrading a contract
- wrapping integration test on devnet
Added
- the data save path of
MxOpsis now configurable through the config varDATA_PATH - chain-simulator network and adapted transaction schema (forward chain until transaction completion)
FileFuzzerStep- Account's addresses are now saved within the scenario data at load time. They can be referenced to with "%account_id.address"
SetVarsStepGenerateWalletsStepR3D4FaucetStepChainSimulatorFaucetStepLoopStepcan now directly use a list from the Scenario dataChainSimulatorFaucetStepandR3D4FaucetStepcan now directly use a list from the Scenario data as targetsWaitStep- classes for smart values to rationalize the conversion of smart values
- Formulas can be directly supplied as arguments within MxOps scenes
- chain-simulator can be started and stopped from MxOps
- results for smart-contract calls can now be saved too
- skip simulator transaction signature when the sender account is unknown
AccountCloneStep- a file cache system per network
- account cloning now use the cache system
- id can now be given to any account
- user accounts are now auto reloaded from scenario data (no need to supply them at each execution)
- SceneStep can now be repeated
- SceneStep can now target a folder of scenes
- User can now evaluate an expression with the data CLI
- logs are now saved to the MxOps data folder and scenario folders
SetSeedStepAssertStepLogStep
Changed
- 🚨 BREAKING CHANGE 🚨 loop variables from
LoopStepare now saved and accessed with the symbol%instead of$ - 🚨 BREAKING CHANGE 🚨 function result are now saved and accessed with the symbol
%instead of$, and the save key is provided by the user - 🚨 BREAKING CHANGE 🚨 account's addresses can no longer be accessed with "[<account_id>]"
- scenes have now default values for allowed scenarios and allowed networks
- 🚨 BREAKING CHANGE 🚨 removed analyze feature from MxOps
- 🚨 BREAKING CHANGE 🚨 rework the data save structure and introduce versioned data structure
- 🚨 BREAKING CHANGE 🚨 upgrade to the new multiversx-sdk-py 1.0.0 and removal of MxPySerializer
- 🚨 BREAKING CHANGE 🚨 OptionalValue are mandatory now (user must input "null")
- 🚨 BREAKING CHANGE 🚨 Enums format has changed to use the one from the multiversx-sdk-py
- 🚨 BREAKING CHANGE 🚨 MultiValueEncoded format has changed to use the one from the multiversx-sdk-py
- 🚨 BREAKING CHANGE 🚨 ledger account index was dropped as it is not used by multiversx-sdk-py
- upgraded all dependencies
- use uv instead of conda for development and env tests
- 🚨 BREAKING CHANGE 🚨 new class workflow for checks, smart-values and steps
- 🚨 BREAKING CHANGE 🚨 Accounts are now saved by bech32, the name to bech32 translation is done using the storage
- 🚨 BREAKING CHANGE 🚨 ABIS are now stored using a contract bech32
- 🚨 BREAKING CHANGE 🚨 Contracts are now handled using contract bech32 by the Scenario Data
- 🚨 BREAKING CHANGE 🚨 All accounts (user, contracts, internal, external) are now defined under the same "accounts" key in scenes
- use uv for package build
- 🚨 BREAKING CHANGE 🚨 scene_path attribute of SceneStep has been renamed path
- 🚨 BREAKING CHANGE 🚨 cli and smart-values have been moved into dedicated sub-packages
- 🚨 BREAKING CHANGE 🚨 step argument
print_resultswas changed tolog_resultsand is set to True by default - 🚨 BREAKING CHANGE 🚨 renamed
wasm_hashtocode_hash - 🚨 BREAKING CHANGE 🚨 step argument
print_resultwas changed tolog_resultand is set to True by default
Full Changelog: v2.2.0...v3.0.0