v0.5.0 - Signing, sending, balance summary & more

^{Note: It may take ~1 day for the update to land in the Firefox store, and ~5-10 days for the Chrome store due to their review processes.}

• Chrome & Brave: https://chrome.google.com/webstore/detail/joule/aejmoogjdllanidlpfjmmmmimfaficio
• Firefox: https://addons.mozilla.org/en-US/firefox/addon/lightning-joule/
• Opera: Still "Coming Soon" ™ due to their lengthy review process

It's been a couple of months without a release, but don't let that fool you into thinking development had stalled; this release is full of new features & fixes. Hopefully more frequent smaller releases can be expected after this.

I'm also happy to have fresh documentation for WebLN, the standard Joule uses to talk to Lightning apps. You can check those out, and use the demos to try out all of the new goodies at https://webln.dev/

On to the patch notes!

Features / Improvements

• WebLN message signing and verifying has been implemented (#154)
  • You can test these out in the brand new WebLN documentation! https://webln.dev/#/api/sign-message
• On-chain transactions can now be made from the Send panel (#161)
• A new balance breakdown interface is available from the options menu or clicking on certain info icons (#177)
• Optionally choose the fee for channel open transactions (#182)
• Channels can be inspected by clicking on them, and provide a command to close it (#179, #185)
  • We can't close via the REST API due to a bug in LND
• Clicking on your node icon now shows your pubkey & connect info (#170)
• Russian rubles (₽) are now a fiat option (#168)
• Added a Zap Desktop button to onboarding (#190)
• Empty channel lists now suggest opening a channel (#167)

Fixes

• Failed connections to your node now pop up a modal with suggestions on how to fix it (#180)
• Blocks till maturity now shows up correctly on pending channels (#166)
• Transactions with no amount field no longer crash when inspected (#159)
• Transactions from older LND nodes no longer crash when inspected (#169)
• Update packages with known vulnerabilities (#189)
  • None of these were security exploits that put anyone at risk, just preventative house cleaning

---

Massive thanks to @jamaljsr, @callmekurisu, @PJUllrich, and @alepop for their contributions to this release. As always, if you notice any problems with the new version, please open an issue for it.