Beacon v4.4.0

[hui-an-yang]

Thank you for your contribution to Taquito.

Before submitting this PR, please make sure:

• Your code builds cleanly without any errors or warnings
• You have run the linter against the changes
• You have added unit tests (if relevant/appropriate)
• You have added integration tests (if relevant/appropriate)
• All public methods or types have TypeDoc coverage with a complete description, and ideally an @example
• You have added or updated corresponding documentation
• If relevant, you have written a first draft summary describing the change for inclusion in Release Notes.

In this PR, please also make sure:

• You have linked this PR to the issue by putting closes #TICKETNUMBER in the description box (when applicable)
• You have added a concise description on your changes

Release Note Draft Snippet

If relevant, please write a summary of your change that will be suitable for
inclusion in the Release Notes for the next Taquito release.

[github-actions]

A new deploy preview is available on Cloudflare Pages at https://4eefa09c.taquito-test-dapp.pages.dev

[github-actions]

New packages have been deployed to the preview repository at https://npm.preview.tezostaquito.io/.

Published packages:

npm i @taquito/beacon-wallet@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/utils@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/sapling@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/http-utils@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/local-forging@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/signer@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/michelson-encoder@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/tzip12@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/core@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/timelock@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/contracts-library@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/ledger-signer@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/remote-signer@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/taquito@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/rpc@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/wallet-connect@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/tzip16@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/
npm i @taquito/michel-codec@21.0.3-3822428-- --registry https://npm.preview.tezostaquito.io/

[cloudflare-workers-and-pages]

Deploying taquito with    Cloudflare Pages

Latest commit:	8b8b042
Status:	✅  Deploy successful!
Preview URL:	https://39e08b5b.taquito.pages.dev
Branch Preview URL:	https://beacon-v4-4-0.taquito.pages.dev

View logs

[hui-an-yang]

Hey @roxaneletourneau & @GImbrailo
I find Node.js CI / lint-and-test (lts/Jod) (pull_request) to be failing at ci
I've tried cloning a fresh repo check out this branch and use lts/Jod then npm ci, npm run build and npm run test without any issue locally.
Wondering if any of you have any insight of the reason and how to fix it?

[hui-an-yang]

I created issue1252 in actions/setup-node@v4 repo, waiting for information to resolve ci failure before merging in main

[roxaneletourneau]

Hey @roxaneletourneau & @GImbrailo I find Node.js CI / lint-and-test (lts/Jod) (pull_request) to be failing at ci I've tried cloning a fresh repo check out this branch and use lts/Jod then npm ci, npm run build and npm run test without any issue locally. Wondering if any of you have any insight of the reason and how to fix it?

I tried running npm ci with the latest node version on my laptop because I am using Linux like the CI, and I confirm it also failed locally. I had to install missing dependencies to fix it:
sudo apt install -y libusb-1.0-0-dev libudev-dev pkg-config

[hui-an-yang]

I tried running npm ci with the latest node version on my laptop because I am using Linux like the CI, and I confirm it also failed locally. I had to install missing dependencies to fix it:
sudo apt install -y libusb-1.0-0-dev libudev-dev pkg-config

@roxaneletourneau Thank you for confirming it failed locally on linux too, I have updated issue1252 in actions/setup-node@v4 repo and created issue57470 in node repo. Hoping they'll fix it in the upcoming versions.
I'll update our ci to use node v22.13.1 for now and update our readme to suggest it's compatible with v22.13.1 if using anything above on a linux machine please run sudo apt install -y libusb-1.0-0-dev libudev-dev pkg-config to preinstall these dependencies.
Can let me know what do you think with the temporary fix for now while waiting node to response and fix in the future.

[roxaneletourneau]

I tried running npm ci with the latest node version on my laptop because I am using Linux like the CI, and I confirm it also failed locally. I had to install missing dependencies to fix it:
sudo apt install -y libusb-1.0-0-dev libudev-dev pkg-config

@roxaneletourneau Thank you for confirming it failed locally on linux too, I have updated issue1252 in actions/setup-node@v4 repo and created issue57470 in node repo. Hoping they'll fix it in the upcoming versions. I'll update our ci to use node v22.13.1 for now and update our readme to suggest it's compatible with v22.13.1 if using anything above on a linux machine please run sudo apt install -y libusb-1.0-0-dev libudev-dev pkg-config to preinstall these dependencies. Can let me know what do you think with the temporary fix for now while waiting node to response and fix in the future.

Sound like a good plan to me :)