Skip to content

Conversation

@edg-l
Copy link
Contributor

@edg-l edg-l commented Feb 12, 2026

Recently this started happening https://github.com/lambdaclass/ethrex/actions/runs/21960414777/job/63436623972?pr=6009

Summary

  • Bump Kurtosis from 1.10.2 to 1.15.2 in assertoor CI jobs
  • Docker Engine v29 raised the minimum API version to 1.44, breaking Kurtosis 1.10.2 which ships a client supporting only API 1.43
  • Also Bumps hive too due to the same issue
  • Also Ignored flaky recurrent test Invalid Missing Ancestor Syncing ReOrg on cancun

Test plan

  • Assertoor Transaction Check passes in CI
  • Assertoor Blob & Stability Check passes in CI

Docker Engine v29 raised the minimum API version to 1.44.
Kurtosis 1.10.2 ships a client that only supports API 1.43,
causing assertoor CI jobs to fail.
@edg-l edg-l requested a review from a team as a code owner February 12, 2026 19:17
@github-actions
Copy link

🤖 Kimi Code Review

Review Summary

This PR updates the Kurtosis version used in the GitHub Actions workflow from 1.10.2 to 1.15.2.

Security & Correctness

  • No security issues identified - this is a simple version bump for a CI tool
  • Version compatibility: The jump from 1.10.2 to 1.15.2 is significant (5 minor versions). While this appears to be a routine update, verify that:
    • The new version is compatible with the pinned ethereum-package branch (82e5a7178138d892c0c31c3839c89d53ffd42d9a)
    • No breaking changes in Kurtosis affect the test setup

Recommendations

  1. Add verification step: Consider adding a step to verify Kurtosis version post-installation:

    - name: Verify Kurtosis version
      run: kurtosis version
  2. Document rationale: While not required for this change, consider adding a comment explaining why this specific version was chosen (e.g., "Update to latest stable for bug fixes and performance improvements").

The change itself is minimal and appears safe. The workflow will validate the new version through the test execution.


Automated review by Kimi (Moonshot AI) · custom prompt

@edg-l edg-l changed the title chore: bump kurtosis version to 1.15.2 chore(ci): bump kurtosis version to 1.15.2 Feb 12, 2026
@github-actions
Copy link

🤖 Codex Code Review

Looks good. This change only bumps the Kurtosis version used in the CI workflow; no Rust/EVM/consensus code is affected.

Notes:

  1. .github/workflows/pr-main_l1.yaml:190 bumps kurtosis_version from 1.10.2 to 1.15.2. This is safe for code correctness and security but may change CI behavior. If the newer Kurtosis requires additional flags or has breaking changes, CI might fail. Consider confirming compatibility with the pinned ethereum-package commit before merging.

No further issues found.


Automated review by OpenAI Codex · custom prompt

@github-actions
Copy link

🤖 Claude Code Review

Now let me provide the code review:


PR Review: chore(ci): bump kurtosis version to 1.15.2

Summary

This is a straightforward dependency version bump for Kurtosis in the CI workflow. The change is necessary to maintain compatibility with Docker Engine v29, which raised the minimum API version to 1.44.

Review Findings

✅ Positive Aspects

  1. Properly scoped change: The PR addresses a specific compatibility issue with a minimal, targeted fix.

  2. Good documentation: The PR description clearly explains the rationale (Docker Engine v29 API version requirement).

  3. Appropriate test plan: The test plan correctly identifies the two Assertoor jobs that will validate the change.

📝 Observations & Recommendations

1. Version jump magnitude
The bump from 1.10.2 to 1.15.2 is significant (5 minor versions). While justified by the breaking change, consider:

  • Reviewing the Kurtosis changelog between these versions to identify any other breaking changes or new features that might affect the tests
  • Verifying that the ethpandaops/kurtosis-assertoor-github-action@v1 action is compatible with Kurtosis 1.15.2

2. Consistency check
The change only updates one occurrence in .github/workflows/pr-main_l1.yaml. If there are other workflows using Kurtosis, they should also be reviewed and updated:

# Check for other Kurtosis version references
grep -r "kurtosis_version" .github/workflows/

3. Testing considerations

  • The PR marks both test plan items as unchecked. Ensure both CI jobs pass before merging
  • Consider if any timeout configurations need adjustment with the new version
  • Monitor the first few runs carefully for any behavioral changes

🔍 Code Quality

File: .github/workflows/pr-main_l1.yaml:193

kurtosis_version: "1.15.2"

✅ The change is correct and follows the existing format (quoted string).

Security Considerations

✅ No security concerns. This is a version bump of a development/testing tool used in CI, not production code.

Ethereum-Specific Considerations

N/A - This change affects CI infrastructure, not Ethereum execution client logic.

Verdict

LGTM with monitoring recommendation

The change is necessary and correctly implemented. The code looks good. Recommend:

  1. Verifying both Assertoor tests pass in CI
  2. Checking if other workflows need similar updates
  3. Monitoring initial CI runs for any unexpected behavior changes

Sources:

  • PR diff and description provided
  • Workflow file analysis at .github/workflows/pr-main_l1.yaml:190-196

Automated review by Claude (Anthropic) · custom prompt

@edg-l edg-l changed the title chore(ci): bump kurtosis version to 1.15.2 fix(l1): bump kurtosis version to 1.15.2 to fix assertoor ci Feb 12, 2026
@greptile-apps
Copy link

greptile-apps bot commented Feb 12, 2026

Greptile Overview

Greptile Summary

Bumped Kurtosis from 1.10.2 to 1.15.2 in the assertoor CI workflow to resolve Docker Engine v29 compatibility issues. Docker Engine v29 requires Docker API version 1.44 minimum, while Kurtosis 1.10.2 only supports API 1.43, causing CI failures.

Key Changes:

  • Updated kurtosis_version from 1.10.2 to 1.15.2 in .github/workflows/pr-main_l1.yaml:193
  • Affects Assertoor Transaction Check and Blob & Stability Check CI jobs
  • Ensures compatibility with GitHub Actions runners using Docker Engine v29

Issues Found:

  • .github/actions/snapsync-run/action.yml:107 still references Kurtosis 1.10.2 and needs to be updated to 1.15.2 for consistency. This will cause the same Docker API compatibility failures in snapsync assertion tests.

Confidence Score: 4/5

  • Safe to merge with one critical follow-up required
  • The change correctly addresses Docker Engine v29 compatibility by upgrading Kurtosis to 1.15.2, which supports Docker API 1.44. However, an inconsistency exists where .github/actions/snapsync-run/action.yml still references the old version 1.10.2, which will cause the same compatibility issues in snapsync tests. This should be fixed in a follow-up PR or added to this PR.
  • .github/actions/snapsync-run/action.yml needs the same Kurtosis version update from 1.10.2 to 1.15.2

Important Files Changed

Filename Overview
.github/workflows/pr-main_l1.yaml Updated Kurtosis from 1.10.2 to 1.15.2 for Docker Engine v29 compatibility, but .github/actions/snapsync-run/action.yml still references 1.10.2

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

1 file reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

@github-actions github-actions bot added the L1 Ethereum client label Feb 12, 2026
@edg-l edg-l enabled auto-merge February 12, 2026 19:45
@edg-l edg-l force-pushed the fix/bump-kurtosis-version branch from a663e67 to 1a2cab7 Compare February 12, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

L1 Ethereum client

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants