v0.0.29

Features

• Update Satellite, Mission Control and Console to release v0.0.31.
• Deploy modules to Console using the new proposals flow.
• Update IC settings for the Console when adding a controller.

v0.0.28

Fix

• Missing required version field to perform Satellite's configuration updates.

v0.0.27

Features

• CLI support for renamed collection configuration datastore instead of db (softly deprecated).

v0.0.26

Features

• Expose a new endpoint in the administration server to set the controller to the Console for local development purposes.

v0.0.25

Fix

• undefined init module error when updating Console's WASM code in juno-console.

v0.0.24

Features

• Upgrade replica as executing proposal 130083 (except icx-proxy which must be pinned).
• Make replica logging quiet.
• Set-up initial-notary-delay-millis via ic-starter for a faster replica.

Build

• Bump CLI dependencies including @junobuild/config which does not require version in the dev config.

v0.0.23

Features

• Spin-up an little server meant to execute various administration commands that can be useful when developing Juno in junobuild/console.

v0.0.22

Fix

• Console canister ID undefined when re-deploying modules in junobuild/console.

v0.0.21

Features

• After installation of the Console, upload the Satellite, Mission Control and Orbiter for releases.

v0.0.20

Features

This release introduces junobuild/console, a Docker container similar to the junobuild/satellite but specifically tailored to provide the backbone for developing Juno locally. Instead of spinning and monitoring a Satellite, it manages other types of smart contracts, including the Console and Observatory. Additionally, it spins up essential canisters required by the platform, such as the NNS Governance and the CMC canisters.