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

feat(bridge-history-api): update l2geth dependency for Pectra readiness #1601

Conversation

colinlyguo
Copy link
Member

@colinlyguo colinlyguo commented Feb 25, 2025

Purpose or design rationale of this PR

Updating the dependency of l2geth in bridge-history, supporting set code transactions.

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

  • feat: A new feature

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

  • Yes

Breaking change label

Does this PR have the breaking-change label?

  • No, this PR is not a breaking change

Summary by CodeRabbit

  • Chores
    • Refined internal components with updated libraries to enhance performance, stability, and security.
    • Rolled out the latest software update, advancing the release version to v4.4.88.
    • Enhanced GitHub Actions workflow for clearer feedback on uncommitted changes during verification.

Copy link

coderabbitai bot commented Feb 25, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • go.work.sum is excluded by !**/*.sum

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request updates dependency versions in the bridge-history-api/go.mod file and bumps the version tag in common/version/version.go. The mod file changes include dependency updates, removals, and additions aimed at aligning package versions. In the version file, the tag is updated from "v4.4.87" to "v4.4.88", reflecting a new release. Additionally, the GitHub Actions workflow for the bridge history API has been modified to provide clearer feedback on uncommitted changes.

Changes

File(s) Change Summary
bridge-history-api/go.mod - Updated github.com/scroll-tech/go-ethereum from v1.10.14-0.20241011150208-4742882675d8 to v1.10.14-0.20250225152658-bcfdb48dd939
- Updated github.com/VictoriaMetrics/fastcache from v1.12.1 to v1.12.2
- Removed dependencies: github.com/DataDog/zstd, github.com/Microsoft/go-winio
- Updated/added multiple dependencies
common/version/version.go - Updated version tag from "v4.4.87" to "v4.4.88"
.github/workflows/bridge_history_api.yml - Enhanced GitHub Actions workflow to echo uncommitted changes detected during verification, providing clearer feedback on changes.

Possibly related PRs

Suggested labels

bump-version

Suggested reviewers

  • georgehao
  • 0xmountaintop

Poem

I’m a rabbit hopping through the code,
Skipping dependencies on my winding road,
Bumping versions fast with a joyful cheer,
Each commit a step, so bright and clear!
🐇 Happy changes, let’s all give a cheer!

Carrots and code—both make life dear!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov-commenter
Copy link

codecov-commenter commented Feb 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.72%. Comparing base (a6f2457) to head (4a01b11).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1601   +/-   ##
========================================
  Coverage    51.72%   51.72%           
========================================
  Files          157      157           
  Lines        12555    12555           
========================================
  Hits          6494     6494           
  Misses        5497     5497           
  Partials       564      564           
Flag Coverage Δ
bridge-history-api 71.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
bridge-history-api/go.mod (1)

38-38: Addition of mmap-go Dependency.

A new indirect dependency, github.com/edsrzf/mmap-go v1.0.0, has been introduced. Please ensure that its inclusion is necessary and that its usage (if any) is accompanied by appropriate documentation and testing.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c07975a and badc313.

⛔ Files ignored due to path filters (1)
  • bridge-history-api/go.sum is excluded by !**/*.sum
📒 Files selected for processing (2)
  • bridge-history-api/go.mod (4 hunks)
  • common/version/version.go (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • common/version/version.go
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: tests
🔇 Additional comments (9)
bridge-history-api/go.mod (9)

11-11: Update to go-ethereum Dependency Version.

The version of github.com/scroll-tech/go-ethereum has been updated to v1.10.14-0.20250225152658-bcfdb48dd939, which aligns with the PR's objective to update the L2 geth dependency for Pectra readiness. Please verify that any API changes or incompatibilities introduced by this commit are fully tested.


20-20: Bump Fastcache Version.

The dependency for github.com/VictoriaMetrics/fastcache has been incremented from v1.12.1 to v1.12.2. This minor version bump should be checked to ensure that no regressions or breaking changes have been introduced.


33-33: Pinning golang-set to a Specific Commit.

The dependency github.com/deckarep/golang-set is now fixed at commit v0.0.0-20180603214616-504e848d77ea. Confirm that this specific commit is stable and that its functionality meets the project’s requirements.


55-55: Replacement with hashicorp/golang-lru Dependency.

The dependency github.com/hashicorp/golang-lru is now included at version v0.5.5-0.20210104140557-80c98217689d, replacing github.com/holiman/billy. Verify that this replacement meets the expected functionality and performance characteristics.


86-86: Addition of Prometheus TSDB Dependency.

The dependency github.com/prometheus/tsdb has been added at version v0.7.1. Ensure that its integration with your Prometheus metrics setup is working as intended.


88-88: Update in Notify Library.

The dependency github.com/rjeczalik/notify is now updated to v0.9.1, replacing the previous dependency (github.com/rogpeppe/go-internal). Please verify that the updated notify library fulfills your notification requirements without introducing regressions.


91-91: Update to da-codec Dependency.

The dependency github.com/scroll-tech/da-codec has been updated to v0.1.3-0.20250210041951-d028c537b995. Confirm that this update aligns with compatibility and performance expectations within the project.


116-116: Review npipe Version Pinning.

The dependency gopkg.in/natefinch/npipe.v2 is pinned at v2.0.0-20160621034901-c1b8fa8bdcce. Please double-check if this version is still appropriate for the Windows-specific functionalities, or if an upgrade might be warranted for improved stability or features.


117-117: Multiple Versions of urfave/cli Detected.

Both github.com/urfave/cli/v2 (direct dependency on line 13) and gopkg.in/urfave/cli.v1 (indirect dependency on line 117) are present. Please validate that the indirect dependency on version 1 is necessary and does not conflict with the usage of version 2.

Thegaram
Thegaram previously approved these changes Feb 25, 2025
@colinlyguo colinlyguo merged commit 5b6b145 into develop Feb 26, 2025
6 checks passed
@colinlyguo colinlyguo deleted the update-l2geth-dependency-in-bridge-history-for-pectra-readiness branch February 26, 2025 07:36
This was referenced Feb 26, 2025
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.

4 participants