mirror of https://github.com/lightninglabs/loop
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2.1 KiB
2.1 KiB
Loop Client Release Notes
This file tracks release notes for the loop client.
Developers:
- When new features are added to the repo, a short description of the feature should be added under the "Next Release" heading.
- This should be done in the same PR as the change so that our release notes stay in sync!
Release Manager:
- All of the items under the "Next Release" heading should be included in the release notes.
- As part of the PR that bumps the client version, cut everything below the 'Next Release' heading.
- These notes can either be pasted in a temporary doc, or you can get them from the PR diff once it is merged.
- The notes are just a guideline as to the changes that have been made since the last release, they can be updated.
- Once the version bump PR is merged and tagged, add the release notes to the tag on GitHub.
Next release
- Fixed compile time compatibility with
lnd v0.12.0-beta
.
New Features
- If lnd is locked when the loop client starts up, it will wait for lnd to be unlocked. Previous versions would exit with an error.
- Loop will no longer need all
lnd
subserver macaroons to be present in the--lnd.macaroondir
. Instead the new--lnd.macaroonpath
option can be pointed to a single macaroon, for example theadmin.macaroon
or a custom baked one with the exact permissions needed for Loop. If the now deprecated flag/option--lnd.macaroondir
is used, it will fall back to use only theadmin.macaroon
from that directory.
Breaking Changes
- The
AutoOut
,AutoOutBudgetSat
andAutoOutBudgetStartSec
fields in theLiquidityParameters
message used in the experimental autoloop API have been renamed toAutoloop
,AutoloopBudgetSat
andAutoloopBudgetStartSec
. - The
autoout
flag for enabling automatic dispatch of loop out swaps has been renamed toautoloop
so that it can cover loop out and loop in. - The
SuggestSwaps
rpc call will now fail with aFailedPrecondition
grpc error code if no rules are configured for the autolooper. Previously the rpc would return an empty response.