-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #120 from carlaKC/clear-release
release notes: clear from last release and fixup
- Loading branch information
Showing
1 changed file
with
16 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,26 +1,28 @@ | ||
| # Loop Client Release Notes | ||
| This file tracks release notes for the loop client. | ||
| # Faraday Client Release Notes | ||
| This file tracks release notes for the faraday 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! | ||
| * 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. | ||
| * 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 | ||
|
|
||
| #### New Features | ||
|
|
||
| #### Breaking Changes | ||
| - Bumped the minimum required version of `lnd` to `v0.11.1-beta`. | ||
|
|
||
| #### Bug Fixes | ||
| - Fixes a bug in how TLS connections were initialized which lead to the | ||
| `missing selected ALPN property` error in node.js and #c clients. | ||
| - A bug where the rpc server would panic on rpc calls to the outlier and | ||
| threshold recommendation apis has been fixed. |