Skip to content

Releases: btcpayserver/btcpayserver

1.13.2

05 Jun 14:40
5884850
Compare
Choose a tag to compare

New features

Bug fixes

Improvements

1.13.1

15 Apr 14:29
ca55e1f
Compare
Choose a tag to compare

Bug fixes

  • Fix: CSV exports from the Reports were exporting dates in 12-hour format instead of 24-hour format. (#5915, #5922) @TChukwuleta
  • Fix: Crash when configuring BTCPay Server with a non-default Postgres schema (Fix #5901) @NicolasDorier
  • Fix: A payment request with an amount of 0 no longer causes the payment request's page to crash (#5926) @Kukks

Improvements

  • Prevent unintentional double payouts (#5931, #5913) @dennisreimann
  • The buyerEmail field in a Payment Request's form will now set the email for the payment request (#5926) @Kukks
  • Added Tether as a supporter to the BTCPay Server Foundation (#5891) @rockstardev

1.13.0

28 Mar 13:50
5b31d4d
Compare
Choose a tag to compare

New feature

Improvements

Bug fixes

1.12.5

01 Feb 05:18
a86165a
Compare
Choose a tag to compare

Bug fixes

  • Fix: Emergency fix for stores using Kraken rate source @NicolasDorier

1.12.4

25 Jan 12:25
2111b67
Compare
Choose a tag to compare

Bug fixes

Improvements

  • Checkout v2: Update checkout v2 translations from Transifex and ChatGPT (#5679) @NicolasDorier
  • Checkout v2: Clicking the QR code now copies the full payment URI (#5625 #5627) @dennisreimann
  • Improved checkout page load time by fetching the recommended fee in the background periodically (#5672) @NicolasDorier
  • Clear any previous pending actions of a plugin when you click uninstall (#5577) @Kukks
  • Display the plugin version that was disabled (#5577) @Kukks
  • Show an update button on disabled plugins instead of an install button (#5577) @Kukks
  • If a plugin is scheduled to be installed/updated, it will display which version was scheduled for the update. If a newer version is available than the scheduled one, an option to switch will be shown (#5577) @Kukks
  • Improved fee rate approximation by linear interpolation between known block targets (#5643) @Kukks
  • Prevented creation of payment requests when a wallet is not set up (#5620) @TChukwuleta
  • Hide LN Balance when using an internal node and not a server admin (#5639) @Kukks
  • Added a link to the Greenfield API Key management page from the store's settings Access token page (#5635) @hiluan
  • Removed the 'What's New' button and information (#5608 #5618) @hiluan

1.12.3

22 Dec 05:32
f23078d
Compare
Choose a tag to compare

Bug fixes

1.12.2

22 Dec 02:00
e84e575
Compare
Choose a tag to compare

Please also see v1.12.1 which was released at the same time.

Bug fixes

1.12.1

21 Dec 15:03
ebc053a
Compare
Choose a tag to compare

Recommended update for users using Boltcard with pull payments or Top-Up invoices.

Breaking change: Boltcards linked to pull payments in version 1.12.0 are not compatible with version 1.12.1.

New Features

  • A disabled plugin can now be uninstalled in the UI (#5570) @Kukks

Bug fixes

  • Fix: Payments to Top-Up could go undetected due to a race condition (#5568) @NicolasDorier
  • Lightning: Fixed the connection display name in LN settings (#5569) @dennisreimann
  • Prevent redirection to archived store after login (#5566) @dennisreimann
  • Use PullPaymentId to derive the cardkey of a Boltcard (#5575) @NicolasDorier
  • Greenfield: The Link a boltcard to a pull payment route would not generate new keys for the boltcard when onExisting was set to UpdateVersion. @NicolasDorier

Improvements

1.12.0

19 Dec 12:10
6ecfe07
Compare
Choose a tag to compare

Noteworthy

  • With this release we upgrade to .NET 8, which also requires a current version of the Docker engine for docker deployments (>= 20.10.10).
    We will try to migrate outdated versions when upgrading BTCPay Server, but if you see these symptoms after updating, please upgrade Docker engine manually.
  • We changed a lot of things under the hood, making the Lightning integrations extendible by plugins and also preparing the
    migration of Altcoins to plugins. If you are using plugins, you will most likely find them disabled after this update, because
    new versions compatible with BTCPay Server v1.12 are required. Please see the "Manage Plugins" section once updated.
  • We are ending support for Postgresql 11 as it reached 5 years after its initial release. Read more about end-of-life (EOL) of postgresql. While Postgresql 11 should still work with BTCPay Server, we will not keep compatibility moving forward.

New feature

  • Webhooks: Support for Payment Requests, Payouts and extendibility by plugins (#5421) @Kukks
  • Support BIP129 Multisig wallet import (#5389) @Kukks
  • POS Keypad: Add plus and change clear functionality (#5396) @dennisreimann @dstrukt
  • Forms: Support adjusting invoice amount by multiplier, enables percentage-based discount codes (#5463) @Kukks
  • Can pair or reset a Boltcard to a pull payment (#5419) @NicolasDorier
  • Plugins: Allow scheduling installs/updates of future plugins (#5537) @Kukks

Bug fixes

Improvements

1.11.7

18 Oct 11:08
a921504
Compare
Choose a tag to compare

New feature

Bug fixes

  • The payments report wasn't properly accounting for Liquid assets and some altcoins (#5388 #5371) @Kukks
  • Switching currencies in the checkout page may have inversed Amount Due and Recommended Fee (#5390) @dennisreimann
  • Reporting now properly formats decimals (#5363) @dennisreimann
  • API docs: Fix several errors and warnings (#5380) @ai-oleynikov
  • Fix Poloniex and Ripio rate provider (#5365) @Kukks
  • Removed unused Argoneum and Exchangerate.host rate provider (#5365) @Kukks
  • Fix: If a store was accepting USDt, invoices wouldn't be processed properly. @Kukks
  • Email rules, Recipients required even if "send mail to buyer" (#5345 #5357) @dennisreimann
  • Fix: BTCPayServer.HostedServices.BitpayIPNSender fail to send notifications on some locale (Fix #5361) @AdilElFarissi

Improvements