Skip to content

chore: prep cl#3043

Merged
julienrbrt merged 1 commit intomainfrom
julien/cl
Feb 3, 2026
Merged

chore: prep cl#3043
julienrbrt merged 1 commit intomainfrom
julien/cl

Conversation

@julienrbrt
Copy link
Member

Overview

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

The latest Buf updates on your PR. Results from workflow CI / buf-check (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed⏩ skipped✅ passed✅ passedFeb 3, 2026, 12:04 PM

@claude
Copy link
Contributor

claude bot commented Feb 3, 2026

Claude finished @julienrbrt's task in 1m 58s —— View job


Code Review Complete ✓

Overview

This PR prepares a release candidate (v1.0.0-rc.2) by updating version references across multiple Go modules and adding a changelog section. The changes are minimal and focused on version management.


Summary of Changes

Files Changed:

  • CHANGELOG.md: Added v1.0.0-rc.2 section header
  • Multiple go.mod files: Updated github.com/evstack/ev-node dependency from v1.0.0-rc.1 → v1.0.0-rc.2
  • Multiple go.sum files: Updated checksums for the new version

Code Quality & Architecture ✅

Positive:

  • Changes follow idiomatic Go module version management
  • Consistent version updates across all dependent modules
  • Proper use of semantic versioning (moving from rc.1 to rc.2)

Concerns:

  1. Inconsistent Version Updates ⚠️

    While the main ev-node dependency was updated to v1.0.0-rc.2, the following dependencies remain at v1.0.0-rc.1:

    • github.com/evstack/ev-node/core v1.0.0-rc.1 (appears in apps/evm/go.mod:13, apps/grpc/go.mod:11, apps/testapp/go.mod:5, execution/evm/go.mod:6)
    • github.com/evstack/ev-node/execution/evm v1.0.0-rc.1 (appears in apps/evm/go.mod:14)
    • github.com/evstack/ev-node/execution/grpc v1.0.0-rc.1 (appears in apps/grpc/go.mod:12)

    Question: Should these sub-packages also be bumped to v1.0.0-rc.2? If not, please clarify the versioning strategy for sub-modules in the PR description.

  2. Empty PR Description 📝

    The PR body contains only "## Overview" with no details. For a release preparation PR, it would be helpful to include:

    • What changes are being released in rc.2
    • Why this release candidate is needed
    • Any breaking changes or important notes
    • Reference to the changelog entries
  3. Module Version Consistency Check 🔍

    The root go.mod at /home/runner/work/ev-node/ev-node/go.mod:15 shows:

    require (
        github.com/evstack/ev-node/core v1.0.0-rc.1

    This suggests the core module may not have been updated. Consider whether all internal modules should be versioned together.


CHANGELOG Review 📋

Positive:

  • Follows Keep a Changelog format
  • Has clear section organization
  • Includes PR references for traceability

Issues:

  1. Incomplete v1.0.0-rc.2 Section ⚠️

    The v1.0.0-rc.2 section (CHANGELOG.md:12-19) only has a "### Changes" subsection with items that appear to be already merged PRs. Missing:

    • No "### Added" or "### Fixed" sections if applicable
    • No date for the release
    • Unclear if all changes since rc.1 are captured

    The changelog shows PRs fix(cache,store): improve cache handling #3030, fix(metrics): proper count of pending blobs metrics #3038, and refactor(store): replace go-header store by ev-node store #3036 but doesn't indicate if these are the only changes since rc.1.

  2. Formatting Inconsistency

    Line 18 uses markdown link format [#3038] while line 19 doesn't maintain consistent link formatting. Should be:

    - Replace `go-header` store by `ev-node` store. This avoid duplication of all blocks in `go-header` and `ev-node` store. Thanks to the cached store from [#3030](https://github.com/evstack/ev-node/pull/3030), this should improve p2p performance as well. ([#3036](https://github.com/evstack/ev-node/pull/3036))
  3. Grammar Issue

    Line 19: "This avoid duplication" → "This avoids duplication"


Documentation & Developer Experience 📚

Missing Context:

  1. No explanation in the PR of why rc.2 is being cut
  2. No release checklist or verification steps
  3. No indication of what testing was performed
  4. The commit title "chore: prep cl" is vague - what does "cl" mean? (Changelog? Candidate Launch?)

Recommendations:

  • Add a detailed PR description explaining the purpose
  • Consider adding a release checklist template
  • Use more descriptive commit messages (e.g., "chore: prepare v1.0.0-rc.2 release")

Testing & Reliability ℹ️

Observation:

  • No test changes required (appropriate for a version bump)
  • Consider verifying that all modules build correctly with the new versions
  • Recommend running integration tests before merging

Verification Command:

make test-all

Security ✅

No security concerns with these changes - they are purely version management updates.


Recommendations

Critical (Must Address)

  1. Clarify version strategy: Should sub-modules (core, execution/evm, execution/grpc) also be v1.0.0-rc.2?
  2. Complete the changelog: Add any missing changes and fix grammar/formatting issues
  3. Add PR description: Explain what's included in rc.2 and why it's being released

Important (Should Address)

  1. Consistent version management: Run go mod tidy on all modules to ensure consistency
  2. Commit message: Consider amending to be more descriptive
  3. Run comprehensive tests: Verify make test-all passes before merging

Nice to Have

  1. Add release notes or a summary of what's new in rc.2
  2. Consider tagging strategy - will this PR result in a git tag?

Questions for Author

  1. Is this PR missing any version updates for internal sub-modules?
  2. What prompted the need for rc.2 vs. proceeding to a final v1.0.0 release?
  3. Are there any migration steps users need to take when upgrading from rc.1 to rc.2?
  4. Should the changelog include a date for when rc.2 will be released?

Final Assessment

Status: ⚠️ Needs Clarification

This PR appears to be a routine version bump, but has several areas needing clarification:

  • Incomplete version updates (sub-modules)
  • Sparse changelog entry
  • Missing PR context

The changes themselves are clean and follow Go conventions, but the release preparation seems incomplete. Please address the version consistency question and enhance the documentation before merging.


@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @julienrbrt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on preparing for the v1.0.0-rc.2 release candidate. It involves updating the project's internal ev-node dependency across various applications and modules to this new version, alongside the necessary updates to the changelog and Go module checksums. This ensures all components are aligned with the latest release candidate.

Highlights

  • Changelog Update: A new section for v1.0.0-rc.2 has been added to CHANGELOG.md, preparing for the upcoming release candidate.
  • Dependency Version Bump: The github.com/evstack/ev-node dependency has been updated from v1.0.0-rc.1 to v1.0.0-rc.2 across multiple go.mod files within various applications and modules.
  • Checksum Updates: Corresponding go.sum files (apps/testapp/go.sum and execution/evm/go.sum) have been updated to reflect the new dependency version and its cryptographic checksums.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • CHANGELOG.md
    • Added a new version header "v1.0.0-rc.2" to mark the upcoming release candidate.
  • apps/evm/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
  • apps/grpc/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
  • apps/testapp/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
  • apps/testapp/go.sum
    • Updated the cryptographic checksums for github.com/evstack/ev-node to match the v1.0.0-rc.2 version.
  • execution/evm/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
  • execution/evm/go.sum
    • Updated the cryptographic checksums for github.com/evstack/ev-node to match the v1.0.0-rc.2 version.
  • execution/evm/test/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
  • test/e2e/go.mod
    • Updated the github.com/evstack/ev-node dependency from v1.0.0-rc.1 to v1.0.0-rc.2.
Activity
  • No human activity (comments, reviews, or explicit progress updates) has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@julienrbrt julienrbrt merged commit 5787f4d into main Feb 3, 2026
24 of 25 checks passed
@julienrbrt julienrbrt deleted the julien/cl branch February 3, 2026 12:05
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request prepares for the v1.0.0-rc.2 release. The changes correctly update module versions across the repository. I've added one suggestion to improve the CHANGELOG.md file by updating the release comparison links, which is a standard practice for maintaining a clear and navigable changelog.


## [Unreleased]

## v1.0.0-rc.2
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To complete the changelog update for the new release, the link definitions at the bottom of the file should be updated. This involves adding a new link for v1.0.0-rc.2 and updating the [Unreleased] link to compare against this new version.

For example:

[Unreleased]: https://github.com/evstack/ev-node/compare/v1.0.0-rc.2...HEAD
[v1.0.0-rc.2]: https://github.com/evstack/ev-node/compare/v1.0.0-rc.1...v1.0.0-rc.2

This will ensure that the changelog remains easy to navigate for users and contributors.

@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 55.96%. Comparing base (709d4db) to head (dffcf47).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3043      +/-   ##
==========================================
- Coverage   56.05%   55.96%   -0.10%     
==========================================
  Files         117      117              
  Lines       11844    11844              
==========================================
- Hits         6639     6628      -11     
- Misses       4475     4486      +11     
  Partials      730      730              
Flag Coverage Δ
combined 55.96% <ø> (-0.10%) ⬇️

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.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

2 participants