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

docs(examples/cbdc): upgrade web3 from v1.5.2 to v1.10.1 #3154

Merged
merged 1 commit into from
Mar 30, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 28, 2024

  1. This had to be done because of security vulnerabilities in the old version.
  2. Originally the robots have attempted to send a pull request with the
    same change but it somehow went haywire and upgraded dozens of other
    versions in dozens of other packcages not the intended one...
  3. So this was manually created to address that bug in GitHub's
    dependabot.
  4. The original commit message did not mention which vulnerabilities
    are being fixed by it and I also cannot remember the specific ones but
    the older versions of web3 were definitely being affected and therefore
    it is known to be a good idea what the bot has proposed even though it
    couldn't explain itself.

Signed-off-by: Peter Somogyvari [email protected]

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 28, 2024
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/web3-utils-1.5.3 branch from 5cca7e8 to 381bbf1 Compare March 29, 2024 03:57
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/web3-utils-1.5.3 branch from 381bbf1 to 575066c Compare March 29, 2024 08:34
Copy link
Contributor

@outSH outSH left a comment

Choose a reason for hiding this comment

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

@petermetz Something's wrong with dependabot, it matched newer packages and propsoed to downgrade them :/ Thanks @izuru0 for noticing it

@petermetz
Copy link
Contributor

@petermetz Something's wrong with dependabot, it matched newer packages and propsoed to downgrade them :/ Thanks @izuru0 for noticing it

@outSH Whoah. This is how the takeover starts. :-)

I'll edit the PR

@petermetz
Copy link
Contributor

├─ @hyperledger/cactus-example-cbdc-bridging-backend@workspace:examples/cactus-example-cbdc-bridging-backend
│  ├─ @hyperledger/cactus-api-client@workspace:packages/cactus-api-client (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-cmd-api-server@workspace:packages/cactus-cmd-api-server (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-plugin-ledger-connector-besu@workspace:packages/cactus-plugin-ledger-connector-besu (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-plugin-ledger-connector-fabric@workspace:packages/cactus-plugin-ledger-connector-fabric (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-plugin-ledger-connector-xdai@workspace:packages/cactus-plugin-ledger-connector-xdai (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-plugin-object-store-ipfs@workspace:extensions/cactus-plugin-object-store-ipfs (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-plugin-satp-hermes@workspace:packages/cactus-plugin-satp-hermes (via npm:2.0.0-alpha.2)
│  ├─ @hyperledger/cactus-test-tooling@workspace:packages/cactus-test-tooling (via npm:2.0.0-alpha.2)
│  ├─ web3-core@npm:1.5.2 (via npm:1.5.2)
│  │  ├─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-eth-iban@npm:1.5.2 (via npm:1.5.2)
│  │  │  │  └─ web3-utils@npm:1.5.2 (via npm:1.5.2)
│  │  │  └─ web3-utils@npm:1.5.2 (via npm:1.5.2)
│  │  ├─ web3-core-method@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-core-subscriptions@npm:1.5.2 (via npm:1.5.2)
│  │  │  │  └─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  └─ web3-utils@npm:1.5.2 (via npm:1.5.2)
│  │  ├─ web3-core-requestmanager@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-providers-http@npm:1.5.2 (via npm:1.5.2)
│  │  │  │  └─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  ├─ web3-providers-ipc@npm:1.5.2 (via npm:1.5.2)
│  │  │  │  └─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  │  └─ web3-providers-ws@npm:1.5.2 (via npm:1.5.2)
│  │  │     └─ web3-core-helpers@npm:1.5.2 (via npm:1.5.2)
│  │  └─ web3-utils@npm:1.5.2 (via npm:1.5.2)
│  ├─ web3-utils@npm:1.5.2 (via npm:1.5.2)

@petermetz petermetz force-pushed the dependabot/npm_and_yarn/web3-utils-1.5.3 branch from 575066c to ecd2fbd Compare March 29, 2024 19:18
@petermetz petermetz changed the title build(deps): bump web3-utils from 1.5.2 to 1.5.3 docs(examples/cbdc): upgrade web3 from v1.5.2 to v1.10.1 Mar 29, 2024
@petermetz petermetz requested a review from outSH March 29, 2024 19:19
Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

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

LGTM

@petermetz
Copy link
Contributor

@outSH, @izuru0 Please check now! I trimmed it down and made it so that only the intended upgrades are being performed.

@petermetz petermetz enabled auto-merge (rebase) March 29, 2024 19:20
Copy link
Contributor

@izuru0 izuru0 left a comment

Choose a reason for hiding this comment

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

LGTM thanks

@petermetz petermetz force-pushed the dependabot/npm_and_yarn/web3-utils-1.5.3 branch from ecd2fbd to 25df562 Compare March 30, 2024 16:26
1. This had to be done because of security vulnerabilities in the old version.
2. Originally the robots have attempted to send a pull request with the
same change but it somehow went haywire and upgraded dozens of other
versions in dozens of other packcages not the intended one...
3. So this was manually created to address that bug in GitHub's
dependabot.
4. The original commit message did not mention which vulnerabilities
are  being fixed by it and I also cannot remember the specific ones but
the older versions of web3 were definitely being affected and therefore
it is known to be a good idea what the bot has proposed even though it
couldn't explain itself.

Signed-off-by: Peter Somogyvari <[email protected]>
@petermetz petermetz force-pushed the dependabot/npm_and_yarn/web3-utils-1.5.3 branch from 25df562 to 4f2c6af Compare March 30, 2024 16:29
@petermetz petermetz merged commit db1aef8 into main Mar 30, 2024
131 of 144 checks passed
@petermetz petermetz deleted the dependabot/npm_and_yarn/web3-utils-1.5.3 branch March 30, 2024 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants