v0.0.37
Summary
In response to the recent cost increase for creating new canisters on the Internet Computer (from 0.1 TCycles to 0.5 TCycles, a +400% increase, proposal 134032), this release adjusts the allocation of cycles for new modules, increasing from 1.1 TCycles to 1.6 TCycles. Consequently, the pricing for addition...
v0.0.36
Summary
This release focuses on client-side improvements, with no new versions of the modules (smart contracts) included. The Console frontend has been migrated to Svelte v5 (few leftovers for future iterations). A new feature has been added, allowing users to receive ICP from OISY directly within the Console
Overview
| Module | Versio...
v0.0.35
Summary
This release brings two features to the Console: enabling developers to spin up Satellites or Orbiters in the subnet of their choice and adding the ability to send ICP from your wallet to the outside world.
Overview
| Module | Version | Breaking changes | | ---------------------------------------------------- | ------- | -------...
v0.0.34
Summary
This release primarily introduces new performance metrics, the collection of Web Vitals, to the Analytics modules. Additionally, it adds new count documents and assets to the Satellites.
Additionally, a patch for the DFINITY ic_cdk crate has been rolled out across all smart contracts to prevent a potential inherited memory leak ([source](https://github.com/dfinity/cdk-rs/pull/50...
v0.0.33
Summary
This release addresses a non-critical but still annoying issue introduced in the Console with the migration to a single smart contract architecture in version v0.0.31. Specifically, since that release, the resources served by the Console were not being gzipped, causing clients to download larger files and resulting in a slight...
v0.0.32
Summary
While this release includes over 100 commits, it does not introduce major new features. Instead, it focuses on incremental improvements, including enhancements in the Satellites and the addition of useful features in Juno's Console.
This release also finalizes the removal of the CLI tool DFX across the entire Juno ecosystem. DFX was often a proven pain, leading to productivity iss...
v0.0.31
Summary
This release of Juno introduces several significant improvements, particularly in the Console, as we prepare for potential decentralization.
Key updates include a shift to a single canister architecture, the implementation of stable memory, and a new proposal mechanism for changes.
Overview
| Module | Version | Breaking change...
v0.0.30
Summary
This new release contains two breaking changes and several new features.
Important note:
👉 If you are using Analytics, Datastore, or Storage, this release introduces major changes that require you to update the JavaScript libraries of your project simultaneously with upgrading your smart contracts!
Breaking Changes ⚠️
New version field
The major techni...
v0.0.29
Summary
When I finalized the release v0.0.28 by upgrading my own projects, starting with cycles.watch, I unexpectedly felt that I "lost" user and heap data.
It turned out that while the migration test from v0.0.15 to v0.0.16 was successful, extending it to an older version of the satellite, v0.0.11, and changing the default m...
v0.0.28
Summary
The major change introduced by this release is the decision to use stable memory as the default strategy for new collections in the Datastore and to manage users created for authentication purposes. This change is backward compatible, meaning that existing satellites will not be affected. If you already have users stored on the heap, they will remain on the heap, but any new satellit...
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 ...
v0.0.26
Summary
Introducing serverless functions! 🚀
Functions are a set of Rust-based features enabling developers to extend the native capabilities of Satellites. Functions facilitate the creation and management of responsive, serverless behaviors within Satellites. Triggered by specific events like document and asset operations, they allow developers to embed custom logic directly into the blo...
v0.0.25
Summary
This release brings improvements to Analytics. Due to the Internet Computer's max ingress message size of 2MB, it was observed that the Analytics dashboard could only display metrics and aggregations for around 11,000 page views within a selected time frame. This lim...
v0.0.24
Summary
In addition to various tooling improvements and fixes, this release introduces two significant changes:
-
The fees for creating new satellites and orbiters were previously fixed at 0.5 ICP ("as constants"). However, in response to the remarkable rise in the coin's market value, this version allows these constants to be manually adjusted.
-
In response to developer feedback co...
v0.0.23
Summary
There was an issue in the upgrade process of Orbiter v0.0.3, which was released in the previous version v0.0.21. This bug had the effect of preventing the upgrade from being completed.
This release fixes the issue with PR #343, and the related wasm code available for updating in the CDN has been [patched](bb6ca2c720804b52...
v0.0.22
Summary
There was a bug in the upgrade process of Mission Control v0.0.8, which was released in the previous version v0.0.21. This bug had the effect of unlinking the Analytics Orbiter smart contract from its Mission Control.
To mitigate the propagation of this issue, the wasm code available for update in the CDN has been [patche...
v0.0.21
Summary
This release introduces numerous enhancements to the hosting features of the Satellite, making it the most powerful hosting smart contract available on the Internet Computer to date. You can explore all the new options in the documentation.
In addition, it brings several new features, including the ability to tran...
v0.0.20
Summary
This release introduces the highly anticipated stable memory feature. For more detailed information, please refer to our documentation at https://juno.build/docs/miscellaneous/memory.
Overview
| Module | Version | Breaking changes |
|---|---|---|
| Satellite | 0.0.12 | |
| ... |
v0.0.19
Summary
Several enhancements and new features have been developed for the console's UI, with no changes to the smart contract.
Among those improvements, a minor breaking change has been implemented. The URL /observatory has been deprecated in favor of /monitoring.
Overview
| Module | Version | Breaking changes | | --- | --- ...
v0.0.18
Summary
This release aims to launch and publicly introduce Juno Analytics 🚀.
Overview
| Module | Version | Breaking changes |
|---|---|---|
| Orbiter | v0.0.2 | ⚠️ |
Notes:
- The Orbiter was available under a flag, so no developers should have used it thus far. As a result, the breaking changes should have no impact ...
v0.0.17
Summary
This release lays the foundation for an easy-to-use and privacy-friendly alternative to Google Analytics within the Juno ecosystem, specifically on the IC.
While the feature is fully functional, it requires real-world testing, which will be conducted on the mainnet. Consequently, it won't be immediately visible through navigation links within Juno's console. Instead, we will initi...
v0.0.16
Summary
Introducing the ability to upgrade satellites and mission controls directly within the Juno's console ("in the browser"), providing an alternative option for users who prefer to use the terminal less frequently. While the CLI upgrade is still available, this new feature enables a seamless upgrade process within the browser.
Additionally, the source fo...
v0.0.15
Summary
This version introduces the ability to edit the names of satellites in the console and also includes a new "rewrite URL" option to enhance the behavior of satellites on the web.
Both the satellite and mission control code are updated.
No breaking changes.
Overview
| Module | Version | Breaking changes | | --- | --...
v0.0.14
Summary
This release addresses few inconsistencies in the core JS libraries (see breaking changes) and introduces various enhancements to the console.
There are no updates to the satellite and mission control code, so there is no need to upgrade to a new version.
Overview
| Module | Version | Bre...
v0.0.13
| Summary |
|---|
| - Fixes an issue in the satellite's listDocs and listAssets feature when pagination is used. |
| - Improves performance of asset uploads. |
| - Few UX improvements in the console, including a brand new onboarding process for satellite creation. |
Juno
Build
- bump IC Rust libs
- switch from
ic-cdk-optimizertoic-wasm
Satellite
###...
v0.0.12
Breaking Changes
This new release of Juno introduces two breaking changes related to listDocs and listAssets.
- the parameters and results of both have functions have been updated
Checkout the release notes of the libraries for more information 👉 release notes
This means that if you upgrade your satellite, you wil...
v0.0.11
Juno
Juno is Open for Everyone. Hello Devs 👋
Console
- remove
invitation_codefrominit_user_mission_control_centerendpoint.
Note: we keep the code and information in stable memory for the moment.
v0.0.10
Observatory
- new canister that takes care of the monitoring (see https://juno.build/docs/miscellaneous/monitoring)
Juno
Features
- new
Observatorypage to enable or disable monitoring, provide an email for notifcations and threshold - improve top-up user experience by providing information about the mission control balance ...
v0.0.9
Juno
Features
internetcomputer.orgfor II per default (with temporary fallback option toic0.app)- support for NFID in authentication section of the console
- remove
noindexand accept crawling to fix Google Search Console warnings - do not bubble warning/error is user cancel sign-in
- display a backdrop when sign-in in progress
Build
- upload Candid files as artif...
v0.0.8
Juno
Breaking Changes
- controllers are migrated from a list of IDs to a list of IDs+data. That way "profile" (a name, a hint) can be set to controllers. It becomes easier to know which controllers was used where. This is a breaking changes in the structure and endpoints.
Used to be:
pub type Controllers = Hashset<Principal>;
New:
pub type Controllers ...