build(deps): bump @solana/web3.js from 1.95.5 to 1.95.8

[dependabot]

Bumps @solana/web3.js from 1.95.5 to 1.95.8.

Release notes

Sourced from @​solana/web3.js's releases.

v1.95.8

1.95.8 (2024-12-03)

Earlier today, a publish-access account was compromised for @solana/web3.js, a JavaScript library that is commonly used by Solana dapps. This allowed an attacker to publish unauthorized and malicious packages that were modified, allowing them to steal private key material and drain funds from dapps, like bots, that handle private keys directly. This issue should not affect non-custodial wallets, as they generally do not expose private keys during transactions. This is not an issue with the Solana protocol itself, but with a specific JavaScript client library and only appears to affect projects that directly handle private keys and that updated within the window of 3:20pm UTC and 8:25pm UTC on Tuesday, December 2, 2024.

These two unauthorized versions (1.95.6 and 1.95.7) were caught within hours and have since been unpublished.

We are asking all Solana app developers to upgrade to version 1.95.8. Developers pinned to latest should also upgrade to 1.95.8.

Developers that suspect they might be compromised should rotate any suspect authority keys, including multisigs, program authorities, server keypairs, and so on.

Commits

• 52e144a chore: bump mocha from 10.8.2 to 11.0.1 (#3667)
• 5b37988 chore: bump typedoc from 0.27.1 to 0.27.2 (#3657)
• 01d4664 chore: bump rollup from 4.27.4 to 4.28.0 (#3656)
• 6b14de8 chore: bump typedoc from 0.27.0 to 0.27.1 (#3647)
• 1799cb9 chore: bump mockttp from 3.15.4 to 3.15.5 (#3646)
• 6bbf467 chore: bump prettier from 3.4.0 to 3.4.1 (#3635)
• ef27bf5 chore: bump typedoc from 0.26.11 to 0.27.0 (#3634)
• d6e0aec chore: bump prettier from 3.3.3 to 3.4.0 (#3627)
• 0d21830 chore: bump jayson from 4.1.2 to 4.1.3 (#3626)
• 4907d7e chore: bump @​noble/hashes from 1.5.0 to 1.6.1 (#3623)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mergify]

automerge label removed due to a CI failure

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.