The Vue release still passed the NPM_TOKEN secret, set 2026-06-08 for
the package's first publish. That token has expired, so `npm publish`
for 1.1.0 failed with E404 on the PUT. Drop the token so the workflow
authenticates through trusted publishing (OIDC), as release.yml does.

The Vue release still passed the NPM_TOKEN secret, set 2026-06-08 for
the package's first publish. That token has expired, so `npm publish`
for 1.1.0 failed with E404 on the PUT. Drop the token so the workflow
authenticates through trusted publishing (OIDC), as release.yml does.

# [1.3.0](https://github.com/TxnLab/use-wallet-ui/compare/v1.2.1...v1.3.0) (2026-11-05)

### Features

* support @txnlab/use-wallet v5 ([15c01e9](https://github.com/TxnLab/use-wallet-ui/commit/15c01e95e72db5950fa7c07e7f9b3cbba84f7cfe))

`npm install -g npm@latest` started installing npm 12, which requires
Node ^22.22.2. CI ran Node 22.22.0 from .nvmrc, so both release
workflows have failed with EBADENGINE since npm 12.0 (2026-07-08).

Move to Node 24.22.2, whose bundled npm 11.19.1 supports trusted
publishing, and drop the global npm update step from both release
workflows. npm now changes only with .nvmrc, so a new npm major can't
silently break releases again. Move the Renovate Node and @types/node
pins to 24.x.

`npm install -g npm@latest` started installing npm 12, which requires
Node ^22.22.2. CI ran Node 22.22.0 from .nvmrc, so both release
workflows have failed with EBADENGINE since npm 12.0 (2026-07-08).

Move to Node 24.22.2, whose bundled npm 11.19.1 supports trusted
publishing, and drop the global npm update step from both release
workflows. npm now changes only with .nvmrc, so a new npm major can't
silently break releases again. Move the Renovate Node and @types/node
pins to 24.x.

* feat: support @txnlab/use-wallet v5

Widen the use-wallet peer range to ^4.6.0 || ^5.0.0 and render
availableWallets in ConnectWalletMenu, falling back to wallets on v4.
Move examples and docs to the v5 adapter packages and bump the Vue
package to 1.1.0.

* chore(examples): make Web3Auth network configurable

Pass web3AuthNetwork from VITE_WEB3AUTH_NETWORK, defaulting to
sapphire_devnet. The network must match the Web3Auth project the
client ID belongs to.

* fix(examples): get Web3Auth example working with web3auth v10

Exclude the process module polyfill so readable-stream (pulled in by
Web3Auth v10) gets the real `process` package with `nextTick`. Serve
the dev server on 127.0.0.1, since Web3Auth's session service rejects
the `localhost` hostname.

* chore(deps): require algosdk 3.7+ to match use-wallet core

use-wallet core has peer-required algosdk ^3.7.0 since 5.1.0, but the
workspace resolved 3.5.2. Bump the examples to ^3.7.0 and the packages'
devDependency to 3.9.0, and note the requirement in the READMEs.

* chore(deps): update use-wallet to 5.1.3 and run Web3Auth example on TestNet

5.1.2 fixes Web3Auth connect (tweetnacl default export) and 5.1.3 makes
Web3Auth available on every network, so the Web3Auth example can use
TestNet like the others.