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-providers-http from 1.8.2 to 1.10.0 #220

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Jun 1, 2023

Snyk has created this PR to upgrade web3-providers-http from 1.8.2 to 1.10.0.

ℹ️ 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 4 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-05-10.
Release notes
Package name: web3-providers-http
  • 1.10.0 - 2023-05-10

    Fixed

    • Improved the error propagation in web3-providers-http package to effectively propagate useful error infomation about failed HTTP connections (#5955)
    • Fixed "Uncaught TypeError" calling a contract function that revert using MetaMask (#4454) and related "n.data.substring is not a function", that is raised when there is a revert and web.eth.handleRevert = true (#6000)

    Changed

    • transaction.type is now formatted to a hex string before being send to provider (#5979)
    • When sending a transaction, if transaction.type === '0x1' && transaction.accessList === undefined, then transaction.accessList is set to [] (#5979)
    • Removed an unnecessary chainId parameter from toChecksumAddress() function types (#5888)

    Added

    • Added support for getPastEvents method to filter allEvents and specific event (#6015)

    Security

    • Updated dependencies (#6044)
  • 1.10.0-rc.0 - 2023-05-02

    Fixed

    • Improved the error propagation in web3-providers-http package to effectively propagate useful error infomation about failed HTTP connections (#5955)
    • Fixed "Uncaught TypeError" calling a contract function that revert using MetaMask (#4454) and related "n.data.substring is not a function", that is raised when there is a revert and web.eth.handleRevert = true (#6000)

    Changed

    • transaction.type is now formatted to a hex string before being send to provider (#5979)
    • When sending a transaction, if transaction.type === '0x1' && transaction.accessList === undefined, then transaction.accessList is set to [] (#5979)
    • Removed an unnecessary chainId parameter from toChecksumAddress() function types (#5888)

    Added

    • Added support for getPastEvents method to filter allEvents and specific event (#6015)

    Security

    • Updated dependencies (#6044)
  • 1.9.0 - 2023-03-20

    Fixed

    • Fixed skipped ws-ganache tests (#5759)
    • Fixed "provider started to reconnect error" in web3-provider-ws (#5820)
    • Fixed Error: Number can only safely store up to 53 bits (#5845)
    • Fixed types for packages which have default exports but not declared default export in .d.ts (#5866)
    • Fixed Transaction type by adding missing properties (#5856)

    Changed

    • Add optional hexFormat param to getTransaction and getBlock that accepts the value 'hex' (#5845)
    • utils.toNumber and utils.hexToNumber can now return the large unsafe numbers as BigInt, if true was passed to a new optional parameter called bigIntOnOverflow (#5845)
    • Updated @ types/bn.js dependency to 5.1.1 in web3, web3-core and web3-eth-contract as reason mentioned in #5640 (#5885)
    • Add description to error for failed connection on websocket (#5884)

    Security

    • Updated dependencies (#5885)
  • 1.9.0-rc.0 - 2023-03-07

    Fixed

    • Fixed skipped ws-ganache tests (#5759)
    • Fixed "provider started to reconnect error" in web3-provider-ws (#5820)
    • Fixed Error: Number can only safely store up to 53 bits (#5845)
    • Fixed types for packages which have default exports but not declared default export in .d.ts (#5866)
    • Fixed Transaction type by adding missing properties (#5856)

    Changed

    • Add optional hexFormat param to getTransaction and getBlock that accepts the value 'hex' (#5845)
    • utils.toNumber and utils.hexToNumber can now return the large unsafe numbers as BigInt, if true was passed to a new optional parameter called bigIntOnOverflow (#5845)
    • Updated @ types/bn.js dependency to 5.1.1 in web3, web3-core and web3-eth-contract as reason mentioned in #5640 (#5885)
    • Add description to error for failed connection on websocket (#5884)

    Security

    • Updated dependencies (#5885)
  • 1.8.2 - 2023-01-30

    Changed

    • Updated Webpack 4 to Webpack 5, more details at (#5629)
    • crypto-browserify module is now used only in webpack builds for polyfilling browsers (#5629)
    • Updated ethereumjs-util to 7.1.5 (#5629)
    • Updated lerna 4 to version 6 (#5680)
    • Bump utils 0.12.0 to 0.12.5 (#5691)

    Fixed

    • Fixed types for web3.utils._jsonInterfaceMethodToString (#5550)
    • Fixed Next.js builds failing on Node.js v16, Abortcontroller added if it doesn't exist globally (#5601)
    • Builds fixed by updating all typescript versions to 4.1 (#5675)

    Removed

    • clean-webpack-plugin has been removed from dev-dependencies (#5629)

    Added

    • https-browserify, process, stream-browserify, stream-http, crypto-browserify added to dev-dependencies for polyfilling (#5629)
    • Add readable-stream to dev-dependancies for webpack (#5629)

    Security

    • npm audit fix for libraries update (#5726)
from web3-providers-http GitHub release notes
Commit messages
Package name: web3-providers-http

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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