v0.5.1

Features

• Check the Satellite version before deployment to ease the release process. This allows developers who haven’t upgraded their Satellite yet to continue deploying. It also enables rolling out GitHub Actions support without requiring everyone to upgrade their suite immediately.

v0.5.0

Features

This update is part of the main Juno release v0.0.51. See the related release notes for full context and details.

v0.4.0

Fix

This release reverts the changes introduced in v0.3.0. While the previous implementation wasn't fundamentally incorrect, it caused issues when the CLI was used through GitHub Actions.

In such cases, the controller often only has READ+WRITE privileges, which are insufficient to query the Internet Computer’s canister_status for memory information. As a result, using our custom endpoints is a more reliable solution.

Reverting the changes resolves the issue.

v0.3.0

Features

• Replace usage of custom memory_size() endpoints with IC management memory metrics data. This is used in juno deploy to assert that the heap size does not overflow, ensuring safe upgrades.
• Removed the guard that limited the above checks to recent Satellites (> v0.0.14), since IC management calls are available for all modules.

Note: This is not a breaking change per se, but I’ve bumped the reduced semver accordingly to make the change more visible for historical purposes.

v0.2.16

Features

• Auto-approve upgrade if only one newer release is found.

v0.2.15

Fix

• juno dev start was always generating a new docker-compose.yml file with a reference to a JSON config file. This happened because the Docker configuration needs to be aware of the Juno config type (JS, TS, or JSON), and likewise, the Juno config must specify which image — Skylab or Satellite — is being used.

v0.2.14

Features

• Replace custom implementation to clean version with minVersion from semver lib.
• Use Juno crates v0.1.0 in Rust template for juno dev eject.

v0.2.13

Features

• Generate and append new juno:package custom section to WASM when building serverless functions in Rust (still support juno:build for backwards compatibility).

v0.2.12

Features

• Support for configuring projects for development using either a production-like setup or a minimal setup via juno dev start, even for projects that are not yet configured.

Note: As a result, the configuration templates have been updated to include both production and development settings.

Example:

import {defineConfig} from '@junobuild/config';

export default defineConfig({
  satellite: {
    ids: {
      development: '<DEV_SATELLITE_ID>',
      production: '<PROD_SATELLITE_ID>'
    },
    source: '<SOURCE>',
    predeploy: ['<COMMAND> build']
  }
});

v0.2.11

Features

• Don't exit hot reload while wathcing build on JS/TS compile errors.