Version 0.16.1 - Mainnet 6 (March 10)

This version of the emulator implements the same functionality as the Mainnet 6 network.

🐞 Bug Fixes

• Update to Cadence v0.13.5-no-id-caching and Flow Go v0.14.9 (#38) @turbolent

Version 0.16.0

💥 Breaking Changes

Update to Flow Go v0.14.8 (#37) @turbolent

This PR in v0.14.6 fixes a bug in the way transaction signatures are ordered on a transaction. This change only affects users of the Go SDK who were using advanced multi-sig functionality.

🛠 Improvements

• Update to Cadence v0.13.5 (#37) @turbolent

v0.15.0

🛠 Improvements

• Update to Cadence v0.13.0, Go SDK v0.15.0, and Flow Go f21d550c6ab0 (#34) @turbolent

🐞 Bug Fixes

• Push Docker images to gcr.io/flow-container-registry (#31) @turbolent
• Fixed CLI links (#32) @magusfabius

v0.14.2

🛠 Improvements

• Log deployed contracts and add a flag to turn on fees (#28) @janezpodhostnik
• Update to Cadence v0.12.6, Go SDK v0.14.3, and Flow Go v0.14.0 (#30) @turbolent

v0.14.1

🛠 Improvements

• Synchronize labels from YAML file (#24) @psiemens
• Use new GitHub Actions Docker actions to build and push images (#25) @turbolent

🐞 Bug Fixes

• Update to Cadence v0.12.5, Go SDK v0.14.2, and Flow Go f166b2a7aa23 (#27) @turbolent

v0.14.0

SDK Compatibility

Flow Go SDK v0.12.x	Flow Go SDK v0.13.x	Flow Go SDK v0.14.x
❌	❌	✅

💥 Breaking Changes

Update to Cadence v0.12

This release updates Cadence from version 0.10 to version 0.12 (0.12.3), along with the Go SDK to version 0.14.1, and Flow Go to commit 79985711a957 (#14, #23).

Cadence v0.11 contained breaking changes, so please read its release notes and the migration guide for hints on how to upgrade your code if needed.

The Testnet will be updated to Cadence v0.12 in an upcoming spork on Jan 27, 2021!

Storage Capacity

This release also implements and enforces (by default) storage capacity and storage limits.

Please test deployment of your contracts and interactions with them when storage limits are enforced.
When the storage limit is exceeded, deposit more FLOW tokens into the account's FLOW vault.

It is not recommended, but you can disable storage limits using the command line option --storage-limit=false.

Storage capacity will start to be enforced in an upcoming spork of the Testnet on Jan 27, 2021!

🛠 Improvements

• Build a Docker image on master pushes and push it to GCR (#5)
• Remove replace statement for CBOR library (#22)

Version 0.12.5

SDK Compatibility

Flow Go SDK v0.11.x	Flow Go SDK v0.12.x	Flow Go SDK v0.13.x
❌	✅	✅

💥 Breaking Changes

• Update to onflow/cadence v0.10.2
• Update to onflow/flow-go-sdk v0.12.2
• Update to onflow/flow-go v0.12.6

Version 0.10.0

SDK Compatibility

Flow Go SDK v0.6.0	Flow Go SDK v0.7.0	Flow Go SDK v0.7.1	Flow Go SDK v0.8.0	Flow Go SDK v0.9.0
❌	✅	✅	✅	✅

🛠 Improvements

Adjust service key configuration logic

Previously it was difficult to determine how the service key flags were being parsed and applied to the emulator configuration. This release updates the logic to be more explicit.

• If either service-priv-key or service-pub-key is passed, the service-sig-algo and service-hash-algo flags must also be set.
• If neither service-priv-key or service-pub-key is passed, a new key is generated using the algorithms specified by service-sig-algo and service-hash-algo.

Remove hardcoded flags from Docker image

Previously the Docker image specified the following CMD entrypoint:

CMD ["emulator", "start", "--init", "--persist"]

This forced the Docker image to always use persistent storage. The --persist flag was removed to allow the user to specify persistence via an environment variable (FLOW_PERSIST=true), and --init was removed because it no longer has any effect now that the emulator is decoupled from the Flow CLI.