Skip to content

Releases: demergent-labs/azle

0.24.1

09 Sep 19:49
a52c7d6
Compare
Choose a tag to compare

0.24.0 had a major issue with the azle bin executable during dfx deploy, which required tsx to be globally installed. This issue has now been resolved.

What's Changed

  • fix global tsx requirement issue for azle's bin by @lastmjs in #2078

Full Changelog: 0.24.0...0.24.1

0.24.1-rc.4

09 Sep 17:47
1d013a4
Compare
Choose a tag to compare
0.24.1-rc.4 Pre-release
Pre-release
azle-bot automated release 0.24.1-rc.4

0.24.1-rc.3

06 Sep 19:13
b5d8dd2
Compare
Choose a tag to compare
0.24.1-rc.3 Pre-release
Pre-release
azle-bot automated release 0.24.1-rc.3

0.24.1-rc.2

06 Sep 17:47
f7ed52a
Compare
Choose a tag to compare
0.24.1-rc.2 Pre-release
Pre-release
azle-bot automated release 0.24.1-rc.2

0.24.1-rc.1

06 Sep 00:02
b4eaf92
Compare
Choose a tag to compare
0.24.1-rc.1 Pre-release
Pre-release
azle-bot automated release 0.24.1-rc.1

0.24.1-rc.0

05 Sep 20:30
6abb0bc
Compare
Choose a tag to compare
0.24.1-rc.0 Pre-release
Pre-release
azle-bot automated release 0.24.1-rc.0

0.24.0

05 Sep 20:36
7c52ab2
Compare
Choose a tag to compare

Features

Stable memory file system

The file system available through fs is now automatically stored in stable memory. This means that upgrading your canister will not wipe your file system. You can store up to 100s of GiBs in one canister, limited by the current maximum stable memory size per canister and the current capacity and free space on the subnet your canister is deployed to.

Experimental flag

The experimental flag has been introduced when using experimental Azle features. If the flag is not set in the dfx.json file or --experimental added to CLI commands, an error will be thrown when using experimental features or experimental CLI commands.

Breaking Changes

  1. The file system is no longer wiped after each upgrade, as it is stored in stable memory
  2. Experimental features and CLI commands now throw an error if the experimental flag is not set (e.g. npx azle new [name] --http-server must now have the --experimental flag)
  3. The --verbose and -v azle CLI options have been removed in favor of only using the AZLE_VERBOSE environment variable
  4. All custom Azle properties in dfx.json are moved into the custom property
  5. AZLE_WASMEDGE_QUICKJS_DIR environment variable has been removed
  6. Running npx azle install-dfx-extension is no longer necessary. Devs must run npm install (or npm install azle) in the same directory as their package.json file before starting up a replica
  7. node_modules/.bin/azle is now used instead of npx azle for Azle build command in the dfx extension.
  8. azle compile [canister name] is now used instead of azle [canister name]
  9. Wasm binary optimization no longer exists (e.g. opt_level in the dfx.json file)
  10. Memory id 254 for StableBTreeMap is now reserved for the stable memory file system

What's Changed

Full Changelog: 0.23.0...0.24.0

0.24.0-rc.9

05 Sep 16:07
442ae37
Compare
Choose a tag to compare
0.24.0-rc.9 Pre-release
Pre-release
azle-bot automated release 0.24.0-rc.9

0.24.0-rc.10

05 Sep 20:01
6d1254a
Compare
Choose a tag to compare
0.24.0-rc.10 Pre-release
Pre-release
azle-bot automated release 0.24.0-rc.10

0.24.0-rc.8

04 Sep 22:41
de7427e
Compare
Choose a tag to compare
0.24.0-rc.8 Pre-release
Pre-release
azle-bot automated release 0.24.0-rc.8