Skip to main content

v0.0.27

Summary

In release v0.0.26 , the access control guard for the memory_size function of the Satellite was mistakenly changed from caller_is_controller to caller_is_admin_controller. This modification, a stronger rule, could cause GitHub Actions that use controllers with Read+Write permissions to fail, as the endpoint is accessed by the CLI (evident in the failed deployment of the website: (see failing deploy of the website: https://github.com/junobuild/docs/actions/runs/7829161014/job/21360561407).

Considering that most users likely have not updated their smart contracts yet, and given that the WASM can be manually re-upgraded using the CLI, this version resolves the issue and releases the update under the same version number.

In the future, I will announce releases in advance to provide a window for necessary adjustments.

Overview

ModuleVersionBreaking changes
Satellite0.0.15
CratesVersionBreaking changes
junobuild-satellitev0.0.15-patch.1
CLIVersionBreaking changes
@junobuild/cliv0.0.49

Changes

Here is a list of changes included in this release:

Console (Backend)

No changes.

Console (Frontend)

No changes.

Satellite

Function memory_size guard was set back to caller_is_controller - i.e. function can be accessed by ADMIN and Read+Write controllers.

Mission Control

No changes.

Orbiter

No changes.

Observatory

No changes.

Library

No changes.

Crates

No other changes than the one required for the Satellite.

CLI

Please refer to the releases for details.

Plugins

No changes.

GitHub Action

No changes.

Docker

No changes.