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

Upgrade celo deps #227

Merged
merged 27 commits into from
Apr 17, 2024
Merged

Upgrade celo deps #227

merged 27 commits into from
Apr 17, 2024

Conversation

palango
Copy link
Contributor

@palango palango commented Mar 4, 2024

Description

The main focus of this PR is updating @celo/contractkit and related packages, in order to not send deprecated legacy celo transactions.

In prior versions, contractkit sends legacy celo transactions when just the gas price is passed as is the case here. @carterqw2 updated contractkit to send legacy ethereum transactions instead.

In future updates it might make sense to update the oracle to send EIP-1559 transactions.

Some changes include upgrading node and the dockerfiles.

Tested

  • yarn test
  • Tested on a local chain
  • Tested on Baklava

Backwards compatibility

Yes

Copy link

socket-security bot commented Mar 4, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@palango palango force-pushed the palango/upgrade-celo-deps branch 2 times, most recently from 189ca49 to 6e07d1a Compare March 4, 2024 16:21
Copy link

socket-security bot commented Mar 4, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@celo/[email protected] Transitive: environment, network +80 15.3 MB app-tooling
npm/@celo/[email protected] filesystem, network Transitive: environment +147 29.3 MB app-tooling
npm/@celo/[email protected] Transitive: environment, filesystem, shell +45 5.57 MB aaron-clabs
npm/@celo/[email protected] Transitive: environment, filesystem, network +89 17.3 MB app-tooling
npm/@celo/[email protected] Transitive: environment, eval, filesystem, network, shell +180 123 MB app-tooling
npm/@celo/[email protected] Transitive: environment, filesystem, network, shell +189 42.8 MB app-tooling
npm/@types/[email protected] None +2 2.09 MB types
npm/@types/[email protected] None +12 2.19 MB types
npm/@types/[email protected] None +1 486 kB types
npm/@types/[email protected] Transitive: filesystem, network +8 2.4 MB types
npm/[email protected] None 0 351 kB mikemcl
npm/[email protected] environment, filesystem, network Transitive: eval, unsafe +63 2.11 MB ulisesgascon
npm/[email protected] eval Transitive: environment, filesystem +3 757 kB vitaly
npm/[email protected] None +8 11.2 MB josdejong
npm/[email protected] network +3 493 kB node-fetch-bot
npm/[email protected] filesystem Transitive: environment, shell +36 3.41 MB palantir
npm/[email protected] None 0 32.4 MB typescript-bot
npm/[email protected] Transitive: network +24 4.67 MB jdevcs
npm/[email protected] Transitive: environment, eval, filesystem, network +97 11.7 MB jdevcs
npm/[email protected] Transitive: environment, filesystem, network +136 23.9 MB jdevcs
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +218 22.2 MB jdevcs

🚮 Removed packages: npm/@ampproject/[email protected], npm/@azure/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@celo/[email protected], npm/@celo/[email protected], npm/@celo/[email protected], npm/@celo/[email protected], npm/@celo/[email protected], npm/@celo/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@ethersproject/[email protected], npm/@jridgewell/[email protected], npm/@jridgewell/[email protected], npm/@jridgewell/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

@palango palango force-pushed the palango/upgrade-celo-deps branch from dbcc061 to 6aeb878 Compare March 4, 2024 16:28
@palango palango force-pushed the palango/upgrade-celo-deps branch from 2002b97 to 71c50ed Compare March 4, 2024 17:03
@palango
Copy link
Contributor Author

palango commented Mar 4, 2024

@SocketSecurity ignore npm/[email protected]

package.json Show resolved Hide resolved
@palango
Copy link
Contributor Author

palango commented Mar 12, 2024

This is on hold until we figure out if we want to do the changes required in contractkit or here.

@nvtaveras
Copy link
Collaborator

@palango Do you mind adding more context on why are these changes being made, consequences of not adding them, timelines, etc?

@aaronmgdr
Copy link
Member

strongly advice merging this as its upgrading very very very old dependencies.

@bowd
Copy link
Collaborator

bowd commented Mar 14, 2024

@SocketSecurity ignore npm/[email protected]

.circleci/config.yml Outdated Show resolved Hide resolved
@carterqw2 carterqw2 marked this pull request as ready for review April 2, 2024 16:35
@palango palango requested a review from aaronmgdr April 2, 2024 17:54
Copy link
Member

@aaronmgdr aaronmgdr left a comment

Choose a reason for hiding this comment

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

would have said in description that it also moves to pnpm (besides the upgrade) but code seems good

ps only reviewed as there was a request specifically for me to

@palango
Copy link
Contributor Author

palango commented Apr 3, 2024

@bowd @sissnad @nvtaveras From our side this is ready to be merged, but we'd like to have some review from you as well. Regarding the rollout, can we help with that somehow or will you talk to the oracle operators?

@nvtaveras
Copy link
Collaborator

Hey @palango, we've been busy lately with other work but would like to deploy this to one of the testnets and have them run there for a bit before merging. Are you fine holding off until then? My current guess is that we will have capacity to test this in around two weeks from now

@palango
Copy link
Contributor Author

palango commented Apr 10, 2024

@nvtaveras Thanks for the update.
Ideally I'd like to get feedback sooner. One idea @carterqw2 brought up was that we could take care of the test deployment on alfajores ourselves. Would that be ok with you?

@palango
Copy link
Contributor Author

palango commented Apr 10, 2024

@SocketSecurity ignore npm/[email protected]

@palango
Copy link
Contributor Author

palango commented Apr 10, 2024

@SocketSecurity ignore npm/[email protected]

@nvtaveras
Copy link
Collaborator

@nvtaveras Thanks for the update.
Ideally I'd like to get feedback sooner. One idea @carterqw2 brought up was that we could take care of the test deployment on alfajores ourselves. Would that be ok with you?

@palango Sure, go for it, but please do it in Baklava instead, as Alfajores it's supposed to be the stable testnet, in case something breaks :) Also feel free to reach out on discord if you need help

@palango
Copy link
Contributor Author

palango commented Apr 12, 2024

@nvtaveras Thanks for the update.
Ideally I'd like to get feedback sooner. One idea @carterqw2 brought up was that we could take care of the test deployment on alfajores ourselves. Would that be ok with you?

@palango Sure, go for it, but please do it in Baklava instead, as Alfajores it's supposed to be the stable testnet, in case something breaks :) Also feel free to reach out on discord if you need help

We're running this branch on baklava now. Everything seems to work fine and the transactions are now eth compatible.

@palango
Copy link
Contributor Author

palango commented Apr 17, 2024

This is running fine since last Friday, therefore merging.

@palango palango merged commit 28ecb4b into main Apr 17, 2024
4 checks passed
@palango palango deleted the palango/upgrade-celo-deps branch April 17, 2024 12:54
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.

6 participants