Skip to content

feat(tooling): align versioning scheme to 6.19.0#2464

Draft
Carsons-Eels wants to merge 1 commit intoethereum:forks/amsterdamfrom
Carsons-Eels:align_versioning
Draft

feat(tooling): align versioning scheme to 6.19.0#2464
Carsons-Eels wants to merge 1 commit intoethereum:forks/amsterdamfrom
Carsons-Eels:align_versioning

Conversation

@Carsons-Eels
Copy link
Copy Markdown
Contributor

@Carsons-Eels Carsons-Eels commented Mar 10, 2026

🗒️ Description

Align versioning schemes for post-WELD world.

  • Major version bumped to 6.19 to leapfrog EELS current version (5.4.0)
  • Redefined the versioning scheme slightly. BPO forks no longer count towards the FORK version, and are instead part of the PATCH versioning.

🔗 Related Issues or PRs

✅ Checklist

  • All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:
    uvx tox -e static
  • All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
  • All: Considered updating the online docs in the ./docs/ directory.
  • All: Set appropriate labels for the changes (only maintainers can apply labels).
  • Determine best way to do releases from EELS moving forward without referencing deprecated EEST repo

Moving From EEST to EELS Releases

release_fixture_full.yaml and release_fixture_feature.yaml:

  • Change --repo ethereum/execution-spec-tests--repo ethereum/execution-specs
  • Replace EEST_RELEASE_TOKEN secret with github.token (same repo, no cross-repo auth needed)
  • Update step names/comments referencing EEST

hive-consume.yaml:

  • Update fixture URL on line 48 from ethereum/execution-spec-testsethereum/execution-specs

releases.py (consumer code):

  • Add ethereum/execution-specs to supported repos

Client teams:

  • Need to update any hardcoded fixture download URLs from ethereum/execution-spec-tests to ethereum/execution-specs

Cute Animal Picture

Put a link to a cute animal picture inside the parenthesis-->

A Philippine Tarsier - Photo by David Haring License does not indicate usage restrictions.

@Carsons-Eels Carsons-Eels added this to the Post-Osaka Refactoring milestone Mar 10, 2026
@Carsons-Eels Carsons-Eels added C-feat Category: an improvement or new feature E-easy Experience: easy, good for newcomers P-low S-needs-attention Status: needs attention A-tooling Area: Improvements or changes to auxiliary tooling such as uv, ruff, mypy, ... labels Mar 10, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 10, 2026

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 86.24%. Comparing base (26c98b9) to head (f53d6be).

Files with missing lines Patch % Lines
src/ethereum/__init__.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##           forks/amsterdam    #2464   +/-   ##
================================================
  Coverage            86.24%   86.24%           
================================================
  Files                  599      599           
  Lines                36984    36984           
  Branches              3795     3795           
================================================
  Hits                 31895    31895           
  Misses                4525     4525           
  Partials               564      564           
Flag Coverage Δ
unittests 86.24% <0.00%> (ø)

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.


- `COMPAT` is incremented when a release contains a backwards-incompatible change to an EELS' interface (Python API, command line tools, etc.)
- `HARDFORK` is the number of hardforks included in the release after Frontier.
- `HARDFORK` is the number of named hardforks included in the release after Frontier. Parameter-only forks (such as BPO forks) do not increment this value.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Glacier forks are "parameter-only" forks, so you'd need to account for them here.

I'd still prefer to just bump HARDFORK for any hardfork, including BPOs.

Comment on lines +36 to +63
The following table is a hypothetical complete example of all of the releases between `6.19.0rc1.dev1` and `7.20.0`, in order from oldest at the top to the newest at the bottom.

| Fork | Description | Version Number |
| ---------- | ------------------ | ------------------ |
| amsterdam | preview of devnet1 | `6.19.0rc1.dev1` |
| amsterdam | preview of devnet1 | `6.19.0rc1.dev2` |
| amsterdam | preview of devnet1 | `6.19.0rc1.dev3` |
| | | |
| amsterdam | finalize devnet1 | `6.19.0rc1` |
| | | |
| amsterdam | devnet1 bugfix | `6.19.0rc1.post1` |
| amsterdam | devnet1 bugfix | `6.19.0rc1.post2` |
| | | |
| amsterdam | finalize devnet2 | `6.19.0rc2` |
| | | |
| amsterdam | finalize mainnet | `6.19.0` |
| | | |
| amsterdam | BPO fork | `6.19.1` |
| amsterdam | BPO fork | `6.19.2` |
| amsterdam | packaging fix | `6.19.3` |
| | | |
| amsterdam | breaking change | `7.19.0` |
| | | |
| next-fork | preview of devnet1 | `7.20.0rc1.dev1` |
| | | |
| next-fork | finalize devnet1 | `7.20.0rc1` |
| | | |
| next-fork | finalize mainnet | `7.20.0` |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not sure changing the examples adds much, they're effectively the same thing, just bigger numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-tooling Area: Improvements or changes to auxiliary tooling such as uv, ruff, mypy, ... C-feat Category: an improvement or new feature E-easy Experience: easy, good for newcomers P-low S-needs-attention Status: needs attention

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants