akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
a427451b75
lnd.xprv/docs/release-notes/release-notes-0.14.0.md

55 lines
1.9 KiB
Markdown
Raw Normal View History

docs/release-notes: add new in-tree location for release notes In this commit, we add a new folder within the `docs` directory that will house the release notes for all versions of `lnd` going forward. Moving to use `git` for the release notes rather than the normal drafting procedure lets us keep track of the set of changes more consistency over time, lets contributors add their release notes over time, and also means we'll no longer need to do a crunch at the tail end of the release process to fill in the set of release notes. For the 0.13.1 release notes, I've done a scan and added anything that has been merged since the last major version tag. In a follow up change, we'll add a new Github action that fails the build if an entry in the release notes linking to the newly added PR isn't committed as well. Until then, any PRs merged in should ensure that they add an entry within the relevant milestone.
2021-06-22 05:21:42 +03:00
# Release Notes
invoices: return payment address from addholdinvoice
2021-07-17 03:33:00 +03:00
## RPC Server
[Return payment address and add index from
addholdinvoice call](https://github.com/lightningnetwork/lnd/pull/5533).
docs/release-notes: add entry for new release notes pre-submit check
2021-07-16 05:22:12 +03:00
# Build System
docs: update release notes
2021-07-19 19:15:47 +03:00
* [A new pre-submit check has been
added](https://github.com/lightningnetwork/lnd/pull/5520) to ensure that all
PRs ([aside from merge
commits](https://github.com/lightningnetwork/lnd/pull/5543)) add an entry in
the release notes folder that at leasts links to PR being added.
* [A new build target itest-race](https://github.com/lightningnetwork/lnd/pull/5542)
to help uncover undetected data races with our itests.
docs/release-notes: add entry for new release notes pre-submit check
2021-07-16 05:22:12 +03:00
docs: remove warning about pruned nodes This removes a warning in the documentation saying that pruned nodes are not supported. This is no longer the case as [pruning is supported since 0.13](https://github.com/lightningnetwork/lnd/pull/5154). So instead it now says pruning is supported and notes the version and implications of pruning.
2021-07-22 23:19:31 +03:00
# Documentation
* [Outdated warning about unsupported pruning was replaced with clarification that LND **does**
support pruning](https://github.com/lightningnetwork/lnd/pull/5553)
docs: add release notes for #5526
2021-07-15 12:33:56 +03:00
# Misc
* The direct use of certain syscalls in packages such as `bbolt` or `lnd`'s own
`healthcheck` package made it impossible to import `lnd` code as a library
into projects that are compiled to WASM binaries. [That problem was fixed by
guarding those syscalls with build tags](https://github.com/lightningnetwork/lnd/pull/5526).
invoice: unused error check
2021-07-17 16:00:05 +03:00
# Code Health
## Code cleanup, refactor, typo fixes
mod+GitHub: shorten PR template, bump golang to 1.15 The golang version always needs to be in sync between the go.mod, the PR checklist and the installation instructions. We also shorten the Pull Request template by removing everything that we have a CI check for and just refer to those checks instead.
2021-07-20 10:32:53 +03:00
invoice: unused error check
2021-07-17 16:00:05 +03:00
* [Unused error check
mod+GitHub: shorten PR template, bump golang to 1.15 The golang version always needs to be in sync between the go.mod, the PR checklist and the installation instructions. We also shorten the Pull Request template by removing everything that we have a CI check for and just refer to those checks instead.
2021-07-20 10:32:53 +03:00
removed](https://github.com/lightningnetwork/lnd/pull/5537).
* [Shorten Pull Request check list by referring to the CI checks that are
docs: minor fixes to contribution guidelines
2021-07-20 16:57:43 +03:00
in place](https://github.com/lightningnetwork/lnd/pull/5545).
* [Added minor fixes to contribution guidelines](https://github.com/lightningnetwork/lnd/pull/5503).
Fix typos in `dest_custom_records` comment
2021-07-18 22:22:19 +03:00
* [Fixed typo in `dest_custom_records` description comment](https://github.com/lightningnetwork/lnd/pull/5541).
invoice: unused error check
2021-07-17 16:00:05 +03:00
docs: update release notes
2021-07-20 16:16:04 +03:00
## Database
* [Ensure single writer for legacy
code](https://github.com/lightningnetwork/lnd/pull/5547) when using etcd
backend.
docs: update release notes
2021-07-19 20:21:23 +03:00
[Optimized payment sequence generation](https://github.com/lightningnetwork/lnd/pull/5514/)
to make LNDs payment throughput (and latency) with better when using etcd.
docs/release-notes: add new in-tree location for release notes In this commit, we add a new folder within the `docs` directory that will house the release notes for all versions of `lnd` going forward. Moving to use `git` for the release notes rather than the normal drafting procedure lets us keep track of the set of changes more consistency over time, lets contributors add their release notes over time, and also means we'll no longer need to do a crunch at the tail end of the release process to fill in the set of release notes. For the 0.13.1 release notes, I've done a scan and added anything that has been merged since the last major version tag. In a follow up change, we'll add a new Github action that fails the build if an entry in the release notes linking to the newly added PR isn't committed as well. Until then, any PRs merged in should ensure that they add an entry within the relevant milestone.
2021-06-22 05:21:42 +03:00
# Contributors (Alphabetical Order)
docs: minor fixes to contribution guidelines
2021-07-20 16:57:43 +03:00
* ErikEk
* Zero-1729
docs: remove warning about pruned nodes This removes a warning in the documentation saying that pruned nodes are not supported. This is no longer the case as [pruning is supported since 0.13](https://github.com/lightningnetwork/lnd/pull/5154). So instead it now says pruning is supported and notes the version and implications of pruning.
2021-07-22 23:19:31 +03:00
* Oliver Gugger
Reference in New Issue Copy Permalink