Skip to content

Latest commit

 

History

History
67 lines (49 loc) · 2.61 KB

CHANGELOG-Sns_Aggregator.md

File metadata and controls

67 lines (49 loc) · 2.61 KB

Changelog SNS Aggregator

All notable changes to the SNS Aggregator will be documented in this file.

The format is based on Keep a Changelog.

The SNS Aggregator is released through proposals in the Network Nervous System. Therefore, each proposal is documented below, following the relevant changes.

Unreleased

Added

Changed

Deprecated

Removed

Fixed

  • Keep existing data when a call to an SNS canister fails.

Security

Security

  • Decoding quota of 10,000 in the http_request method.

Added

  • Include SNS nervous system parameters.
  • Add common code snippets for developers to the "Documentation" chapter on the landing page.

Changed

  • Updated the SNS bindings used by the aggregator.

Changed

  • Updated libraries provided by the ic repository to release-2023-06-07_23-01.

Wasm changes

  • In fast updates, update derived_state and lifecycle as well as the now deprecated swap_state.
  • New field logo in the meta data with the relative path to the logo asset.
  • Add a getting started section in landing page.
  • Various minor style improvements: favicon, spacing, status "open" color and text clamp

Added

  • More tests that the SNS aggregator contains the expected number of SNSs.
  • Display commit, branch name and similar data when deploying to a test canister.

Changed

  • Ensure that the last paginated entry is incomplete.

Fixed

  • Update the path to the nns-sns-wasm .did file.
  • Update the index.html when it has changed.

Added

  • Style (UI design) for the landing page
  • Add a link that points to NNS Dapp GitHub repo
  • Display swaps' lifecycle on the landing page

Changed

  • Updated ic-cdk to the latest version and use the, now separate, ic-cdk-timers.
  • Updated IC commit to 06f339b83ce37e3fc9571e1b4251fbcf5c1a8239, made on Mon July 3 2023.
  • Shortened patch files by namespacing Principal automatically, automating the use of EmptyRecord and using CallResult in API declarations.