Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade web3 from 4.11.0 to 4.11.1 #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

OKEAMAH
Copy link
Member

@OKEAMAH OKEAMAH commented Aug 23, 2024

snyk-top-banner

Snyk has created this PR to upgrade web3 from 4.11.0 to 4.11.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 8 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: web3
  • 4.11.1 - 2024-07-24

    [4.11.1]

    Fixed

    web3-errors

    • Fixed the undefined data in Eip838ExecutionError constructor (#6905)

    web3-eth

    • Adds transaction property to be an empty list rather than undefined when no transactions are included in the block (#7151)
    • Change method getTransactionReceipt to not be casted as TransactionReceipt to give proper return type (#7159)

    web3

    • Remove redundant constructor of contractBuilder (#7150)

    What's Changed

    New Contributors

    Full Changelog: v4.11.0...v4.11.1

  • 4.11.1-dev.e5efe49.0 - 2024-07-22
  • 4.11.1-dev.cbcfc18.0 - 2024-07-22
  • 4.11.1-dev.9afaa61.0 - 2024-07-16
  • 4.11.1-dev.6b80cf0.0 - 2024-07-12
  • 4.11.1-dev.5f6deeb.0 - 2024-07-22
  • 4.11.1-dev.5ad7e5b.0 - 2024-07-17
  • 4.11.1-dev.463d070.0 - 2024-07-11
  • 4.11.0 - 2024-07-11

    [4.11.0]

    Fixed

    web3-eth-abi

    • fix encodedata in EIP-712 (#7095)

    web3-utils

    • _sendPendingRequests will catch unhandled errors from _sendToSocket (#6968)

    web3-eth

    • Fixed geth issue when running a new instance, transactions will index when there are no blocks created (#7098)

    Changed

    web3-eth-accounts

    • baseTransaction method updated (#7095)

    web3-providers-ws

    • Update dependancies (#7109)

    web3-rpc-providers

    • Change request return type Promise<ResultType> to Promise<JsonRpcResponseWithResult<ResultType>> (#7102)

    Added

    web3-eth-contract

    • populateTransaction was added to contract methods (#7124)
    • Contract has setTransactionMiddleware and getTransactionMiddleware for automatically passing to sentTransaction for deploy and send functions (#7138)

    web3-rpc-providers

    • When error is returned with code 429, throw rate limit error (#7102)

    web3

    • web3.eth.Contract will get transaction middleware and use it, if web3.eth has transaction middleware. (#7138)
from web3 GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade web3 from 4.11.0 to 4.11.1.

See this package in npm:
web3

See this project in Snyk:
https://app.snyk.io/org/okeamah/project/7d35db6c-f6d1-4df2-ad10-47318c3a5675?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants