Skip to content
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.

Bump web3.js to 1.2.2 #1277

Merged
merged 12 commits into from
Nov 7, 2019
Merged

Bump web3.js to 1.2.2 #1277

merged 12 commits into from
Nov 7, 2019

Conversation

spalladino
Copy link
Contributor

No description provided.

@nventuro
Copy link
Contributor

nventuro commented Nov 4, 2019

It was my understanding that the latest web3 version comes with typings that work properly - if that's the case, shouldn't we also drop the dependency on @types/web3?

@spalladino
Copy link
Contributor Author

@nventuro CI is finally green. Can I ask for a re-review?

Copy link
Contributor

@nventuro nventuro left a comment

Choose a reason for hiding this comment

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

Looks great! I mostly have questions about things that struck me as odd

.circleci/config.yml Show resolved Hide resolved
<<: *defaults
steps:
- test:
workspace: examples/lib-complex
Copy link
Contributor

Choose a reason for hiding this comment

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

I noticed all of lib-complex, including the CI is setup, is gone. Is this related to the web3 upgrade?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, lib-complex was using outdated versions of everything - it even pulled zos-lib and [email protected]. I spent a few hours trying to upgrade it, and eventually decided to cut it.

"web3": "1.2.1",
"web3-utils": "1.2.0"
"web3": "1.2.2",
"web3-eth": "1.2.2",
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these being added so that they are pinned? They seem to be already pinned on the web3 package itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is what yarn failed to properly hoist. On a clean install, I ended up with web3 1.2.2, web3-eth 1.2.2, but web3-eth-contract 1.2.1. We have a transitive dependency to web3 1.2.1, which is installed within the package that requires it, but that's not the case for web3-eth-contract.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, I see. It'd be great if we were able to document this here. Shame Crockford decided to disallow comments

packages/lib/src/artifacts/Contract.ts Show resolved Hide resolved
packages/lib/src/artifacts/ZWeb3.ts Outdated Show resolved Hide resolved
tests/kits/test/src/integration.test.js Show resolved Hide resolved
@spalladino spalladino merged commit 28dbea4 into master Nov 7, 2019
@spalladino spalladino deleted the dep/web3-1.2.2 branch November 7, 2019 22:36
spalladino added a commit that referenced this pull request Nov 7, 2019
frangio pushed a commit that referenced this pull request Dec 23, 2019
* Bump web3 to 1.2.2

* Remove @types/web3

* Patch typing of web3.eth.getStorageAt

* Fix Web3 contract typings for v1.2.2

* Remove outdated lib-complex

* Use yarn instead of lerna bootstrap on integration test

* Clean up root yarn lock

* Remove lib-complex example from CI

* CI cache bust

* Pin dependencies on web3-eth-contract

* Update required CI checks for mergify

* Update packages/lib/src/artifacts/ZWeb3.ts

Co-Authored-By: Nicolás Venturo <[email protected]>
(cherry picked from commit 28dbea4)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants