Release/6.11.1

[pete-watters]

Try out this version of Leather — download extension builds.

This release contains:

• Ensure full token names show if space available #4170
• Fix state change behavior upon selecting "Send" for inscription #4028
• Wallet always opens to Balances tab #4086
• UI bugs on BITCOIN FOR THE REST OF US page #4374
• Display Ledger incompatibility message for unsupported browsers #4334
• Version Packages #1234
• Improve onboarding design #1232
• [2.9.0] Bug: <describe issue> #1235
• Change out test-personal.id subdomain for id.blockstack #152
• Disable spellcheck for Secret Key textarea on sign in screen #153
• Ensure Secret Key display after user enters invalid then valid username value #150
• Rework Ledger onboarding flow  #4281
• feat: return addresses of regtest and signet #4388

[pete-watters]

I named it 6.11.1 but I'm not sure if that will be the version increment.

I think we should come up with a system to name the releases the same as the tag and version increment. I used GitFlow CLI for this in the past: https://github.com/nvie/gitflow

[kyranjamie]

I think we should come up with a system to name the releases the same as the tag and version increment. I used GitFlow CLI for this in the past: https://github.com/nvie/gitflow

Re your point, this is a limitation of semantic-release. The idea is you don't need to know the version, but it's limiting imo. There's an issue asking for a feature that allows you to know ahead of time what version it'll use, so we could do just this.

[kyranjamie]

I hope the merge back works better this time 🙏🏼

[pete-watters]

I think we should come up with a system to name the releases the same as the tag and version increment. I used GitFlow CLI for this in the past: https://github.com/nvie/gitflow

Re your point, this is a limitation of semantic-release. The idea is you don't need to know the version, but it's limiting imo. There's an issue asking for a feature that allows you to know ahead of time what version it'll use, so we could do just this.

Thanks 👍 I'll take a look and see if I can use dry-run or else a plugin to do this. There is a fork we could potentially use also https://github.com/semantic-release-plus/semantic-release-plus

I take it that semantic-release gives us some benefits and we want to keep using it. It's used by nx-release also which I will test run for the mono repo - https://youtu.be/NQHk7HhP1Uo?feature=shared