Skip to content

Releases: getAlby/hub

v1.22.2 Marc Horowitz

11 May 14:27
Immutable release. Only release title and notes can be modified.
v1.22.2
8616626

Choose a tag to compare

In this release Alby Hub adds a new AI & Agents page, an integrated on-chain wallet mode, custom user labels for transactions, redesigned settings pages, improved budget selection when creating app connections and support for connecting Alby Hub to Core Lightning (our most requested feature!) plus many other bug fixes and minor improvements.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New Features

Fixes

  • fix: update to alby go-nostr fork which reconnects after receiving CLOSED message by @rolznz in #2331
  • fix: allow creating apps without requiring superuser access by @im-adithya in #2316
  • fix: position and size sidebar hint x icon by @im-adithya in #2313
  • fix: incorrect colors in close channel dialog by @rolznz in #2312
  • fix: link colors in themes with brighter primary colors by @rolznz in #2311
  • fix: allow pasting BIP-21 URL into the wallet send input by @rolznz in #2310
  • fix: replace payment flow intermediate screens in browser history by @im-adithya in #2308
  • fix: hide transaction ID from on-chain transactions list by @reneaaron in #2304
  • fix: scope Alby theme default-variant styling to buttons only by @reneaaron in #2302
  • fix: avoid highlighted border on menu buttons in Alby theme by @im-adithya in #2286
  • fix: preserve badge background clipping by @im-adithya in #2273
  • fix: simplify themes by @im-adithya in #2270
  • fix: improve Earn page readability by @reneaaron in #2264
  • fix: auto-balance home dashboard columns by @reneaaron in #2255
  • fix: clarify connected peers navigation in LDK alert by @hermes-alby in #2250
  • fix: remove bzip install command (agent can figure it out) by @rolznz in #2246
  • fix: use npx skills add for agent skill install prompts by @reneaaron in #2236
  • fix: use file paths instead of hex during LND onboarding by @im-adithya in #2231
  • fix: fetch currencies through alby backend api by @im-adithya in #2212
  • fix: one-click connection flow shows waiting screen instead of hanging by @reneaaron in #2211
  • fix: improve budget select UX by @reneaaron in #2209
  • fix: align Pro badge styling with theme by @reneaaron in #2198
  • fix: LND payments made externally from the hub are not visible by @frnandu in #2183
  • fix: remove custom text styles from checbox and radio labels by @reneaaron in #2180
  • fix: update AGENTS.md for common problems in ui development by @reneaaron in #2179
  • fix: avoid blocking startup on boltz websocket by @im-adithya in #2167
  • fix: make HTTP start JWT secret loading idempotent by @im-adithya in #2165
  • fix: update wails in workflow to v2.11.0 by @im-adithya in #2156
  • fix: return app metadata and lud16 in get_info without scope by @im-adithya in #2152
  • fix: unlock error when node is not started by @im-adithya in #2151
  • fix: handle invalid connect peer input gracefully by @im-adithya in #2150

Misc

Read more

v1.21.6 Satoshi Nakamoto

14 Mar 03:56
Immutable release. Only release title and notes can be modified.
v1.21.6
15ef0fb

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Hotfix v1.21.6

In this hotfix we add update the boltz dependency and improve the UX for swap-outs (lightning -> on-chain) to only require 1 on-chain confirmation instead of 2. We also add Alby's new referral program to the earn page, added castamatic to the app store, and did some minor UI improvements.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New Features

Fixes

Misc

  • chore: update PPQ to use alby affiliate link by @rolznz in #2117
  • build(deps): bump github.com/BoltzExchange/boltz-client/v2 from 2.10.0 to 2.11.1 by @dependabot[bot] in #2127

New Contributors

Full Changelog: v1.21.5...v1.21.6

v1.21.5 Satoshi Nakamoto

02 Mar 19:17
Immutable release. Only release title and notes can be modified.
v1.21.5
b984d7a

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Hotfix v1.21.5

In this hotfix we add initial support for stablecoins and crypto onramps and offramps (can be hidden from the settings by enabling "Maxi Mode"). We also add a second relay to the default relay configuration to improve connection quality. several new apps to the app store, such as Alby CLI, PPQ, and LNVPS. We also update LDK dependency to fix a channel disconnection issue with eclair node peers. Also a number of other minor bugs were fixed and dependencies were updated.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New Features

Fixes

Misc

  • docs: add LDK signet config by @rolznz in #2021
  • chore: remove hasLdkDir check by @sergey3bv in #2014
  • chore: remove unused LNClient.ListTransactions method by @joelklabo in #2046
  • chore: update no-token API tests to expect 401 by @im-adithya in #2059
  • chore: remove unused frontend dependencies by @im-adithya in #2063
  • chore: bump ldk node dependencies by @rolznz in #2054
  • chore: migrate to eslint v10 by @im-adithya in #2091
  • chore: update additional places to support multiple relays by @rolznz in #2104
  • chore: make shell scripts POSIX compliant by @sergey3bv in #2015
  • build(deps): bump google.golang.org/grpc from 1.76.0 to 1.77.0 by @dependabot[bot] in #1938
  • build(deps): bump golang.org/x/oauth2 from 0.33.0 to 0.34.0 by @dependabot[bot] in #1964
  • build(deps): bump golang.org/x/crypto from 0.44.0 to 0.45.0 by @dependabot[bot] in #1937
  • build(deps): bump github.com/labstack/echo-jwt/v4 from 4.3.1 to 4.4.0 by @dependabot[bot] in #1954
  • build(deps): bump github.com/BoltzExchange/boltz-client/v2 from 2.9.1 to 2.10.0 by @dependabot[bot] in #1955
  • build(deps): bump @stepperize/react from 5.1.8 to 5.1.9 in /frontend by @dependabot[bot] in #1936
  • build(deps): bump @radix-ui/react-label from 2.1.7 to 2.1.8 in /frontend by @dependabot[bot] in #1932
  • build(deps-dev): bump vite-plugin-pwa from 0.20.5 to 1.1.0 in /frontend by @dependabot[bot] in #1934
  • build(deps-dev): bump @types/node from 24.7.2 to 25.2.3 in /frontend by @dependabot[bot] in #2080
  • build(deps-dev): bump vite-tsconfig-paths from 5.1.4 to 6.1.1 in /frontend by @dependabot[bot] in #2079
  • build(deps): bump tailwind-merge from 3.3.1 to 3.4.1 in /frontend by @dependabot[bot] in #2078
  • build(deps): bump @radix-ui/react-checkbox from 1.3.2 to 1.3.3 in /frontend by @dependabot[bot] in #2077
  • build(deps): bump github.com/sirupsen/logrus from 1.9.3 to 1.9.4 by @dependabot[bot] in #2076
  • build(deps): bump github.com/golang-jwt/jwt/v5 from 5.3.0 to 5.3.1 by @dependabot[bot] in #2074
  • build(deps): bump golang.org/x/crypto from 0.45.0 to 0.48.0 by @dependabot[bot] in #2073
  • build(deps): bump github.com/mattn/go-sqlite3 from 1.14.32 to 1.14.34 by @dependabot[bot] in #2072

New Contributors

Full Changelog: v1.21.4...v1.21.5

v1.21.4 Satoshi Nakamoto

12 Jan 12:58
Immutable release. Only release title and notes can be modified.
v1.21.4
797faa7

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Hotfix v1.21.4

In this hotfix we fix swapping from an external on-chain wallet to lightning from the Node page, and also fix some minor dialog UI/UX issues.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

Fixes

  • fix: conditional query param in swap in status navigation by @im-adithya in #2011
  • fix: enable keyboard submission for dialogs and maximum dialog height #760 by @keshav0479 in #2005

New Contributors

Full Changelog: v1.21.3...v1.21.4

v1.21.3 Satoshi Nakamoto

09 Jan 05:04
Immutable release. Only release title and notes can be modified.
v1.21.3
a5d45cb

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Hotfix v1.21.3

In this hotfix we make some improvements to dynamic channel backups, fix incorrect maximum amount when swapping in from external wallet, and add 2 new apps to the app store.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New features

  • feat: add alert to node page when user has any large LDK channel monitors by @rolznz in #2007
  • feat: add TunnelSats to app store by @TrezorHannes in #2001
  • feat: add fountain to the app store by @rolznz in #2009

Fixes

  • fix: only clear LDK VSS migration config value after successfully starting node by @rolznz in #2000
  • fix: max amount when swapping in from external wallet by @rolznz in #2004
  • fix: increase vss client timeout by @rolznz in #2002

Misc

New Contributors

Full Changelog: v1.21.2...v1.21.3

v1.21.2 Satoshi Nakamoto

18 Dec 13:42
Immutable release. Only release title and notes can be modified.
v1.21.2
1083047

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Hotfix v1.21.2

In this hotfix we update to LDK-Node v0.7.0, which has a number of stability improvements. We also add a few new apps to the app store, and some other minor bugfixes, performance and security improvements.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New features

Fixes

  • fix: Allow Account Settings Page to Load by @netmojo in #1930
  • fix: make sure verify.sh is replaced by last version when downloaded by @Sakrecoer in #1956
  • fix: check lnclient in event handler to avoid crash on shutdown by @rolznz in #1987
  • fix: consistent use of bitcoinDisplayFormat by @reneaaron in #1942
  • fix: check for an error when getting public key when creating new app by @rolznz in #1989

Misc

New Contributors

Full Changelog: v1.21.0...v1.21.2

v1.21.0 Satoshi Nakamoto

21 Nov 16:22
v1.21.0
cdbced9

Choose a tag to compare

In this release Alby Hub is updated to Alby's new branding! other changes include a simpler swaps and on-chain receive UX, multiple relay support, better presets for creating connections, simpler unit display, more accessible keyboard navigation, and many bugfixes and other minor improvements.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New features

Fixes

Misc

  • chore: simplify opened first channel page by @rolznz in #1841
  • chore: add type to routes object by @rolznz in #1840
  • chore: simplified swap in and wallet receive to spending UX by @rolznz in #1836
  • chore: do not print error message if ldk log directory does not exist by @rolznz in #1859
  • chore: Standardize terminology to "recovery phrase" across UI by @Copilot in #1876
  • chore: enable 0-conf for LDK flashsats channels by @rolznz in #1884
  • chore: improve button accessibility by @im-adithya in #1906
  • chore: upgrade react to v1.18.3 by @im-adithya in #1907
  • chore: decouple ldk log by @frnandu in #1879
  • build(deps): bump lucide-react from 0.525.0 to 0.544.0 in /frontend by @dependabot[bot] in #1794
  • build(deps-dev): bump @tailwindcss/typography from 0.5.18 to 0.5.19 in /frontend by @dependabot[bot] in #1795
  • build(deps): bump @radix-ui/react-dialog from 1.1.14 to 1.1.15 in /frontend by @dependabot[bot] in #1796
  • build(deps): bump @radix-ui/react-accordion from 1.2.11 to 1.2.12 in /frontend by @dependabot[bot] in #1809
  • build(deps-dev): bump vite-tsconfig-paths from 4.3.2 to 5.1.4 in /frontend by @dependabot[bot] in #1797
  • build(deps): bump github.com/BoltzExchange/boltz-client/v2 from 2.8.4 to 2.8.9 by @dependabot[bot] in #1826
  • build(deps): bump golang.org/x/crypto from 0.42.0 to 0.43.0 by @dependabot[bot] in #1827
  • build(deps): bump google.golang.org/grpc from 1.75.1 to 1.76.0 by @dependabot[bot] in #1828
  • build(deps-dev): bump @types/node from 20.19.10 to 24.7.2 in /frontend by @dependabot[bot] in #1829
  • build(deps): bump @scure/bip39 from 1.6.0 to 2.0.1 in /frontend by @dependabot[bot] in #1830
  • build(deps): bump golang.org/x/oauth2 from 0.31.0 to 0.32.0 by @dependabot[bot] in #1852
  • build(deps-dev): bump typescript from 5.9.2 to 5.9.3 in /frontend by @dependabot[bot] in #1853
  • build(deps): bump github.com/nbd-wtf/go-nostr from 0.52.0 to 0.52.1 by @dependabot[bot] in #1868
  • build(deps): bump @radix-ui/react-context-menu from 2.2.15 to 2.2.16 in /frontend by @dependabot[bot] in #1854
  • build(deps): bump github.com/BoltzExchange/boltz-client/v2 from 2.8.9 to 2.9.0 by @dependabot[bot] in #1865
  • build(deps-dev): bump tailwindcss from 4.1.13 to 4.1.16 in /frontend by @dependabot[bot] in #1869
  • build(deps): bump github.com/lightningnetwork/lnd from 0.19.3-beta.rc2 to 0.20.0-beta.rc2 by @dependabot[bot] in #1866
  • build(deps): bump @radix-ui/react-hover-card from 1.1.14 to 1.1.15 in /frontend by @dependabot[bot] in #1855
  • build(deps): bump @radix-ui/react-menubar from 1.1.15 to 1.1.16 in /frontend by @dependabot[bot] in #1856
  • build(deps-dev): bump eslint-config-prettier from 9.1.2 to 10.1.8 in /frontend by @dependabot[bot] in #1902
  • build(deps): bump @radix-ui/react-radio-group from 1.3.7 to 1.3.8 in /frontend by @dependabot[bot] in #1905
  • build(deps): bump @radix-ui/react-avatar from 1.1.10 to 1.1.11 in /frontend by @dependabot[bot] in #1904
  • build(deps-dev): bump @commitlint/config-conventional from 19.8.1 to 20.0.0 in /frontend by @dependabot[bot] in #1903
  • build(deps): bump github.com/lightningnetwork/lnd from 0.20.0-beta.rc2 to 0.20.0-beta.rc4 by @dependabot[bot] in #1898
  • build(deps): bump gorm.io/gorm from 1.31.0 to 1.31.1 by @dependabot[bot] in #1897
  • build(deps): bump github.com/btcsuite/btcd/btcec/v2 from 2.3.5 to 2.3.6 by @dependabot[bot] in #1899
  • build(deps): bump github.com/wailsapp/wails/v2 from 2.10.2 to 2.11.0 by @dependabot[bot] in https://g...
Read more

v1.20.0 Robert Hettinga

25 Sep 05:52
v1.20.0
b8d2861

Choose a tag to compare

In this release we have a new connection wizard to guide the user through connecting apps from the app store. You can now also export Alby Hub transactions to CSV (both the main transaction list and individual connections/subwallets). All channels can now be purchased using your preferred payment method (lightning wallet or credit card). There's also a new search dialog and hotkey to easily get to a specific page in the hub. This release also includes many other minor improvements and bug fixes.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

New features

Fixes

  • fix: use InvoicePaid state to mark swap in success by @im-adithya in #1674
  • fix: ldk relax maximum fee estimate confirmation target estimation by @rolznz in #1683
  • fix: use break-anywhere instead of break-words by @rolznz in #1684
  • fix: filter out suggestions that do not allow public channels if the order is for a public channel by @rolznz in #1697
  • fix: set direction in swap alert by @im-adithya in #1715
  • fix: add min width 0 to SidebarInset to stop overflows by @im-adithya in #1710
  • fix: badge usage by @reneaaron in #1725
  • fix: mark failed payment as settled by @rolznz in #1727
  • fix: use LNClient payment context by @rolznz in #1728
  • fix: from and to descriptions in transaction item for zaps and swaps by @rolznz in #1730
  • fix: add min width 0 to flex parents by @im-adithya in #1737
  • fix: alert styling in import mnemonic screen by @im-adithya in #1738
  • fix: Aalert users about anchor-reserve when they try to use their max on-chain balance by @krrish-sehgal in #1748
  • fix: remove finalize step in 1 click flow by @im-adithya in #1743
  • fix: add break-anywhere to description in confirm payment screen by @im-adithya in #1745
  • fix: omit empty fields in NWC get_info response by @krrish-sehgal in #1750
  • fix: ensure boostagrams are valid json before adding to the transaction by @rolznz in #1755
  • fix: decrease size of search input and remove command badge on mobile by @rolznz in #1768
  • fix: fix button keyboard selection on calendar component by @krrish-sehgal in #1773
  • fix: see 1 confirmation and swap id by @krrish-sehgal in #1772

Misc

  • chore: replace divs with shadcn tab component by @im-adithya in #1673
  • chore: use NewRequestWithContext instead of NewRequest by @im-adithya in #1677
  • chore: speed up slow list transactions query by adding updated at index by @rolznz in #1681
  • chore: cleanup on-chain dropdown options by @reneaaron in #1686
  • chore: Add Educational Links to Channel Warning Messages by @NodeDiver in #1688
  • chore: add dependabot for frontend dependencies by @rolznz in #1687
  • chore: remove unused call to get LDK node payment on success event by @rolznz in #1726
  • chore: add note about channels being non-refundable by @rolznz in #1729
  • chore: request channel info + orders from alby oauth endpoint by @im-adithya in #1714
  • chore: always add swap out fees on top by @im-adithya in #1739
  • chore: remove card description for Sub-Wallets by @Dunsin-cyber in #1747
  • chore: removed the fee credit system by @krrish-sehgal in #1769
  • chore: add instructions to the refund swap dialog by @rolznz in #1776
  • chore: update routing fees link on home page forwards widget by @rolznz in #1777
  • build(deps): bump gorm.io/gorm from 1.30.1 to 1.30.2 by @dependabot[bot] in #1676
  • build(deps): bump github.com/stretchr/testify from 1.11.0 to 1.11.1 by @dependabot[bot] in #1675
  • build(deps): bump gorm.io/gorm from 1.30.2 to 1.30.5 by @dependabot[bot] in #1709
  • build(deps): bump google.golang.org/grpc from 1.75.0 to 1.75.1 by @dependabot[bot] in #1720
  • build(deps): bump gorm.io/gorm from 1.30.5 to 1.31.0 by @dependabot[bot] in #1719
  • build(deps): bump github.com/go-gormigrate/gormigrate/v2 from 2.1.4 to 2.1.5 by @dependabot[bot] in #1707
  • build(deps): bump golang.org/x/oauth2 from 0.30.0 to 0.31.0 by @dependabot[bot] in #1701
  • build(deps-dev): bump shx from 0.3.4 to 0.4.0 in /frontend by @dependabot[bot] in #1702
  • build(deps-dev): bump prettier from 3.2.5 to 3.6.2 in /frontend by @dependabot[bot] in #1700
  • build(deps): bump @getalby/sdk from 6.0.0 to 6.0.1 in /frontend by @dependabot[bot] in #1703
  • build(deps): bump swr from 2.3.4 to 2.3.6 in /frontend by @dependabot[bot] in #1706
  • build(deps): bump golang.org/x/crypto from 0.41.0 to 0.42.0 by @dependabot[bot] in #1718
  • build(deps): bump react-resizable-panels from 3.0.4 to 3.0.6 in /frontend by @dependabot[bot] in #1721
  • build(deps): bump gorm.io/datatypes from 1.2.6 to 1.2.7 by @dependabot[bot] in #1756
  • build(deps): bump @stepperize/react from 5.1.6 to 5.1.8 in /frontend by @dependabot[bot] in #1757
  • build(deps-dev): bump @tailwindcss/typography from 0.5.16 to 0.5.18 in /frontend by @dependabot[bot] in #1758
  • build(deps): bump @radix-ui/react-switch from 1.2.5 to 1.2.6 in /frontend by @dependabot[bot] in #1759
  • build(deps-dev): bump tailwindcss from 4.1.11 to 4.1.13 in /frontend by @dependabot[bot] in #1760
  • build(deps): bump react-day-picker from 9.8.1 to 9.11.0 in /frontend by @dependabot[bot] in #1761

New Contributors

Full Changelog: v1.19.3...v1.20.0

v1.19.3 Nadia Heninger

30 Aug 06:04
v1.19.3
f7cdb2b

Choose a tag to compare

In this release Alby Hub adds on-chain and swaps to the wallet send and receive pages, redesigns the app store, adds routing statistics to the homepage, auto-swap to xpub, more seamless first channel flow with support to pay by credit card, and many bug fixes and minor improvements.

Hotfix 1.19.3

In this hotfix, some links are fixed that opened the connections page on the app store tab instead of the connections tab.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

Fixes

  • fix: link to connected apps rather than app store by @rolznz in #1667

Full Changelog: v1.19.2...v1.19.3

v1.19.2 Nadia Heninger

29 Aug 11:29
v1.19.2
2bd8ebd

Choose a tag to compare

In this release Alby Hub adds on-chain and swaps to the wallet send and receive pages, redesigns the app store, adds routing statistics to the homepage, auto-swap to xpub, more seamless first channel flow with support to pay by credit card, and many bug fixes and minor improvements.

Hotfix 1.19.2

In this hotfix, a bug causing auto-swaps to xpub to fail (Note: the lightning payment eventually fails and funds are returned to the wallet) has been fixed. Also, a scrollbar was added to the transaction detail modal, for transactions with lots of details (such as podcasting boostagrams)

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.asc and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.asc manifest.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Jan 8 11:56:42 2025 +07
gpg:                using RSA key 5D92185938E6DBF893DCCC5BA5EABD8835092B08
gpg: Good signature from "Roland Bewick <roland.bewick@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive:

shasum -a 256 <filename>

Compare the hash with the one in the manifest file and ensure they match exactly.

What's Changed

Fixes

Full Changelog: v1.19.1...v1.19.2