docs: Fix wasm-pack URL and update build output listing

[d4wae89d498]

Corrected the URL for 'wasm-pack' and updated the file listing after the build.

[cla-bot]

Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @d4wae89d498 on file. In order for us to review and merge your code, please sign:

• For individual contribution: our CLA
• for Bounty submission, if you are an individual: our T&C
• for Bounty submission, if you are a company: our T&C
  to get yourself added.

If you already signed one of this document, just wait to be added to the bot config.

[aquint-zama]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[IceTDrinker]

Thanks for updating the links to the new official wasm-pack location !

[IceTDrinker]

@d4wae89d498 your commit message does not conform to our standard, please change it to:

chore: Fix wasm-pack URL and update build output listing

[d4wae89d498]

Done

[IceTDrinker]

@d4wae89d498 thanks, it seems we have a small issue at the moment on one of our CI tool, I'll let you know if you need to rebase once we have a fix

[d4wae89d498]

I just made the 'fix' keyword lowercase. I'll wait for your updates.

[IceTDrinker]

@d4wae89d498 we should have a fix for the issue in CI, can you try rebasing on our latest main please ?

[IceTDrinker]

@d4wae89d498 did you see my previous message ? :)

[d4wae89d498]

@IceTDrinker Yes sorry I was busy yesterday. I will do it tonight :)

[IceTDrinker]

no worries @d4wae89d498 :) just be careful I see a potential conflict on one of the files, hopefully the conflict is very small

[d4wae89d498]

@IceTDrinker I guess I just rebased successfully, as promised. I took care of the small conflict, thank you for the heads-up.

[IceTDrinker]

thanks @d4wae89d498 just relaunched the CI

[IceTDrinker]

⚠️ This PR contains unsigned commits. To get your PR merged, please sign those commits (git rebase --exec 'git commit -S --amend --no-edit -n' @{upstream}) and force push them to this branch (git push --force-with-lease).

If you're new to commit signing, there are different ways to set it up:

Sign commits with gpg

Follow the steps below to set up commit signing with gpg:

1. Generate a GPG key
2. Add the GPG key to your GitHub account
3. Configure git to use your GPG key for commit signing

Sign commits with ssh-agent

Follow the steps below to set up commit signing with ssh-agent:

1. Generate an SSH key and add it to ssh-agent
2. Add the SSH key to your GitHub account
3. Configure git to use your SSH key for commit signing

Sign commits with 1Password

You can also sign commits using 1Password, which lets you sign commits with biometrics without the signing key leaving the local 1Password process.

Learn how to use 1Password to sign your commits.

[d4wae89d498]

@IceTDrinker I will do it tonight. Sorry for the mistake. Have a good day 🙂

[IceTDrinker]

no worries

[d4wae89d498]

@IceTDrinker Hello, I just signed the commit.

[IceTDrinker]

hello @d4wae89d498 thanks, I will take a look :)

[IceTDrinker]

seems like, we have another CI issue... we will manage this on our end

[IceTDrinker]

@d4wae89d498 given we may not be able to fix this right away, would you be ok if I open the PR myself by crediting you with co-authored-by https://docs.github.com/articles/creating-a-commit-with-multiple-authors ?

[d4wae89d498]

@IceTDrinker hello yes no problem! I wish you a good day

[IceTDrinker]

superseded by #3166

thanks again, and sorry about the CI issues