Release Notes
v2.12.0
Ledger release v2.12.0
Release date STG: June 10, 2024
Release date PRD: June 17, 2024
CLI improvements
CLI is now supporting new features that were already implemented in API but were not exposed via CLI:
- allow to activate bridge
- allow to update ledger
- allow to drop wallets
- allow to push a "second-party" public key
- allow to set policy for all the records
Additionally:
- we added support for querying record changes in CLI
- when updating records previous data that is not changed is not replaced anymore
- fixed bug when showing the filters in
effect list
(it showedundefined
even when filters existed) - CLI now always requires the secret key unless
--no-secret
flag is passed - remote signers are now always stored locally as well - key pair is stored locally and public key is stored remotely
- replaced
ngrok
withlocaltunnel
- each CLI execution now has its own config directory (.minka dir)
- introduced CLI configuration flag
--config-dir
which specifies.minka
folder path. - implemented support for handles containing
:
via CLI
Ledger SDK
- added
bridge.activate
method to support already added endpointPOST /bridges/:handle/activate
- fixed error with invalid token when reading records with @ in the handle
- fixed concurrency issue with ledger-sdk
.with
method
Improvements & Fixes
- fixed
Active ledger should not be set in context
error that was happening when trying to create a ledger from the CLI - fixed bridge entries structures when non-grouping
- fixed incorrect configuration of
LEDGER_SUBDOMAIN_HANDLE_REGEX
- fixed logging duplication
- fixed query for running jobs on bridge-sdk
- defined access behavior for payloads delivered through effects
- fixed issue with axios brackets encoding
- implemented validation for anchor lookup response schema
- implemented validation that lookup request has consistent wallet
- implemented forwarding of authorization header for proxied requests
- added wallet limit endpoint to openapi spec and published to stoplight
Studio
N/A