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

fix(deps): upgrade eth-json-rpc-filters, eth-json-rpc-engine #9274

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

legobeat
Copy link
Contributor

@legobeat legobeat commented Apr 17, 2024

Description

The runtime dependencies eth-json-rpc-filters and json-rpc-engine are both deprecated. This replaces them with their successors @metamask/eth-json-rpc-filters and @metamask/json-rpc-engine, respectively.

Related issues

Manual testing steps

n/a

Screenshots/Recordings

Before

n/a

After

n/a

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've completed the PR template to the best of my ability
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

This comment was marked as off-topic.

@legobeat legobeat changed the title Deps eth json rpc filters fix(deps): upgrade eth-json-rpc-filters, eth-json-rpc-engine Apr 17, 2024
Copy link

socket-security bot commented Apr 17, 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.

View full report↗︎

@legobeat legobeat added dependencies Pull requests that update a dependency file team-security labels Apr 17, 2024
@legobeat
Copy link
Contributor Author

@SocketSecurity ignore npm/@metamask/[email protected]

Copy link

socket-security bot commented Apr 17, 2024

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

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected] None 0 24.6 kB lgbot

🚮 Removed packages: npm/[email protected]

View full report↗︎

@legobeat legobeat force-pushed the deps-eth-json-rpc-filters branch 4 times, most recently from 53c8a35 to 69be175 Compare April 18, 2024 21:09
@legobeat legobeat added the Run Smoke E2E Triggers smoke e2e on Bitrise label Apr 18, 2024

This comment was marked as outdated.

@legobeat legobeat force-pushed the deps-eth-json-rpc-filters branch 3 times, most recently from a443778 to 9b7463f Compare April 18, 2024 22:03
@legobeat legobeat added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Apr 18, 2024

This comment was marked as outdated.

@legobeat legobeat added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Apr 19, 2024

This comment was marked as outdated.

@legobeat legobeat added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Apr 19, 2024
@legobeat legobeat added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Jun 11, 2024
Copy link
Contributor

github-actions bot commented Jun 11, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 4a914af
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bcc52743-ae03-4059-a97b-abd804453cc0

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@legobeat legobeat added the DO-NOT-MERGE Pull requests that should not be merged label Jun 11, 2024
@legobeat
Copy link
Contributor Author

legobeat commented Jun 11, 2024

@legobeat Still working on this? It looks like based on the CI failures that we might need to bump transaction-controller?

Recently, no. And yes, looks like that is related. Would you know which version of @metamask/transaction-controller would unlock this?

Looking at it now, the mismatching types due to mismatching versions look like they should be resolved by upgrading @metamask/transaction-controller from ^13 to ^15, which implies a bump of @metamask/network-controller to ^15 and its @metamask/json-rpc-middleware from ^11 to ^12.

@legobeat
Copy link
Contributor Author

The failing Check for js or jsx file being added rule seems to FP on changed files and interpreting them as added.

@legobeat

This comment was marked as resolved.

@legobeat legobeat added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Jun 11, 2024
Copy link
Contributor

https://bitrise.io/ Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 8920824
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53b4eec6-1e48-4c84-8fd7-aaa5dcf16513

Note

  • This comment will auto-update when build completes
  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Copy link

sonarcloud bot commented Jun 11, 2024

@metamaskbot
Copy link
Collaborator

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 8920824
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53b4eec6-1e48-4c84-8fd7-aaa5dcf16513

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

3 similar comments
@metamaskbot
Copy link
Collaborator

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 8920824
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53b4eec6-1e48-4c84-8fd7-aaa5dcf16513

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@metamaskbot
Copy link
Collaborator

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 8920824
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53b4eec6-1e48-4c84-8fd7-aaa5dcf16513

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@metamaskbot
Copy link
Collaborator

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 8920824
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53b4eec6-1e48-4c84-8fd7-aaa5dcf16513

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@Mrtenz Mrtenz removed their request for review July 4, 2024 09:12
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 DO-NOT-MERGE Pull requests that should not be merged Run Smoke E2E Triggers smoke e2e on Bitrise team-security
Projects
Status: Needs dev review
Development

Successfully merging this pull request may close these issues.

4 participants