2020-09-10 12:05:36 +00:00
|
|
|
# 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.
|
2020-10-22 18:47:09 +00:00
|
|
|
* 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.
|
2020-09-10 12:05:36 +00:00
|
|
|
|
2020-10-15 07:20:24 +00:00
|
|
|
## Next release
|
|
|
|
|
|
2020-12-01 13:56:16 +00:00
|
|
|
#### New Features
|
2021-02-16 11:31:53 +00:00
|
|
|
* Autoloop can now be configured on a per-peer basis, rather than only on an
|
|
|
|
|
individual channel level. This change allows desired liquidity thresholds
|
|
|
|
|
to be set for an individual peer, rather than a specific channel, and
|
|
|
|
|
leverages multi-loop-out to more efficiently manage liquidity. To configure
|
|
|
|
|
peer-level rules, provide the 'setrule' command with the peer's pubkey.
|
2020-12-01 13:56:16 +00:00
|
|
|
|
2020-10-15 07:20:24 +00:00
|
|
|
#### Breaking Changes
|
|
|
|
|
|
|
|
|
|
#### Bug Fixes
|
