mirror of
https://github.com/btcpayserver/btcpayserver.git
synced 2025-01-18 13:26:47 +01:00
bump
This commit is contained in:
parent
bd73cac1a1
commit
03fbd51fab
@ -1,5 +1,5 @@
|
||||
<Project>
|
||||
<PropertyGroup>
|
||||
<Version>1.6.0</Version>
|
||||
<Version>1.6.1</Version>
|
||||
</PropertyGroup>
|
||||
</Project>
|
||||
|
10
Changelog.md
10
Changelog.md
@ -1,5 +1,15 @@
|
||||
# Changelog
|
||||
|
||||
## 1.6.1
|
||||
|
||||
This fix a critical issue introduced by 1.6.0.
|
||||
If you are using kraken rate provider with altcoins integration, you need to update urgently.
|
||||
|
||||
### Bug fixes:
|
||||
|
||||
* Fix stack overflow if ripio rate provider is unavailable @NicolasDorier
|
||||
* Fix: For some asset pair the kraken rate was inverted (#3957) @NicolasDorier
|
||||
|
||||
## 1.6.0
|
||||
|
||||
In the past six months, we fixed a critical security vulnerability in one of BTCPay's versions. The security vulnerability has been disclosed responsibly, and we granted a bounty to the security researcher who discovered it. As far as we know, this particular vulnerability has not been exploited in the wild as it depends on multiple factors. For security reasons, we will not publicly disclose details yet. Timeframe for public disclosure is 6-12 months. We already have a CVE number reserved for it.
|
||||
|
Loading…
Reference in New Issue
Block a user