chore: require core v1.1.0

[tac0turtle]

Bumps the root module's core requirement v1.0.0 → v1.1.0.

Why

The root module has used core.ExecuteResult / the new Executor.ExecuteTxs signature since #3282, but go.mod still required core v1.0.0 (which has the old signature). It built only because of the local replace github.com/evstack/ev-node/core => ./core. External consumers ignore replace directives, so go get github.com/evstack/ev-node@<tag> resolved core v1.0.0 and failed to compile.

core/v1.1.0 is now published, so require can point at it. The replace stays for in-repo dev.

Context: supersedes v1.2.0

v1.2.0 was tagged before core/v1.1.0 existed, so it froze the stale require core v1.0.0 and is broken for consumers. It's already proxy-cached and therefore immutable, so we roll forward: this PR is the prerequisite for tagging v1.2.1.

Verification

• go build ./... passes
• go mod tidy produces no further diff (go.sum unchanged — local replace needs no checksum)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the required core component version to improve compatibility and access to the latest available updates.

[github-actions]

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

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	⏩ skipped	Jul 20, 2026, 8:36 AM

[coderabbitai]

Warning

Review limit reached

@tac0turtle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ab2a57c1-8ae9-4b02-b1c8-0d2612819506

📥 Commits

Reviewing files that changed from the base of the PR and between 7e7f43d and 617c752.

📒 Files selected for processing (5)

• apps/evm/go.mod
• apps/testapp/go.mod
• execution/evm/go.mod
• execution/evm/test/go.mod
• test/e2e/go.mod

📝 Walkthrough

Walkthrough

Updates the github.com/evstack/ev-node/core dependency in go.mod from v1.0.0 to v1.1.0 and removes its local replacement.

Changes

Core dependency update

Layer / File(s)	Summary
Update core module requirement go.mod	Changes the required core module version from v1.0.0 to v1.1.0 and removes the local replacement directive.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• evstack/ev-node#3135: Updates the same core dependency entry in go.mod.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: bumping the core dependency to v1.1.0.
Description check	✅ Passed	The description covers the change, rationale, context, and verification, though it doesn't use the template's Overview heading.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-core-1.1.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.30%. Comparing base (0e9c60f) to head (617c752).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3391   +/-   ##
=======================================
  Coverage   62.30%   62.30%           
=======================================
  Files         120      120           
  Lines       13454    13454           
=======================================
+ Hits         8382     8383    +1     
- Misses       4129     4130    +1     
+ Partials      943      941    -2     

Flag	Coverage Δ
combined	62.30% <ø> (+<0.01%)	⬆️

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

☔ View full report in Codecov by Harness.
📢 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.