Skip to content
This repository was archived by the owner on Oct 16, 2025. It is now read-only.

bump eth-block-tracker to 12.2.1#422

Merged
jiexi merged 6 commits intomainfrom
jl/bump-eth-block-tracker-12.2.1
Oct 15, 2025
Merged

bump eth-block-tracker to 12.2.1#422
jiexi merged 6 commits intomainfrom
jl/bump-eth-block-tracker-12.2.1

Conversation

@jiexi
Copy link
Copy Markdown
Member

@jiexi jiexi commented Oct 15, 2025


Note

Bumps @metamask/eth-block-tracker to ^12.2.1 and updates the Unreleased changelog accordingly.

  • Dependencies:
    • Bump @metamask/eth-block-tracker from ^12.2.0 to ^12.2.1 in package.json and yarn.lock.
  • Docs:
    • Update CHANGELOG.md Unreleased with a Changed entry noting the bump; retains the recent Fixed note on request processing delays.

Written by Cursor Bugbot for commit 2d440aa. This will update automatically on new commits. Configure here.

@jiexi jiexi requested a review from a team as a code owner October 15, 2025 16:53
@socket-security
Copy link
Copy Markdown

socket-security bot commented Oct 15, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​metamask/​eth-block-tracker@​12.2.0 ⏵ 12.2.199 +1100100 +194 +2100

View full report

yarn.lock Outdated
languageName: node
linkType: hard

"@metamask/eth-block-tracker@npm:^12.2.1":
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Needs a dedupe

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

good catch. Done here 5bfea7d

Gudahtt
Gudahtt previously approved these changes Oct 15, 2025
Copy link
Copy Markdown
Member

@Gudahtt Gudahtt left a comment

Choose a reason for hiding this comment

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

LGTM!

Gudahtt pushed a commit that referenced this pull request Oct 15, 2025
… core monorepo (#420)" (#423)

This reverts commit 5391380.

This breaking change is blocking a release fix that will include:
1. #421
2. #422

Will readd this commit after those two PRs are merged and a patch
release is cut

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?

Are there any issues or other links reviewers should consult to
understand this pull request better? For instance:

* Fixes #12345
* See: #67890
-->
@@ -1,6 +1,3 @@
# This file is generated by running "yarn install" inside your project.
# Manual changes might be lost - proceed with caution!
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🤔

Copy link
Copy Markdown
Member

@Gudahtt Gudahtt Oct 15, 2025

Choose a reason for hiding this comment

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

Maybe try git fetch && git checkout origin/main yarn.lock && yarn dedupe to refresh this again

cursor[bot]

This comment was marked as outdated.

Gudahtt
Gudahtt previously approved these changes Oct 15, 2025
@jiexi jiexi enabled auto-merge (squash) October 15, 2025 17:52
@jiexi jiexi merged commit fcb4ce2 into main Oct 15, 2025
20 checks passed
@jiexi jiexi deleted the jl/bump-eth-block-tracker-12.2.1 branch October 15, 2025 17:52
Mrtenz pushed a commit to MetaMask/core that referenced this pull request Oct 16, 2025
… core monorepo (#420)" (#423)

This reverts commit d10c455.

This breaking change is blocking a release fix that will include:
1. MetaMask/eth-json-rpc-middleware#421
2. MetaMask/eth-json-rpc-middleware#422

Will readd this commit after those two PRs are merged and a patch
release is cut

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?

Are there any issues or other links reviewers should consult to
understand this pull request better? For instance:

* Fixes #12345
* See: #67890
-->
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