feat(ci): create releases in EEST from EELS

[spencer-tb]

🗒️ Description

PR to create releases from EELS to EEST. Tags in EELS for releases must now be prefixed with tests-.

Remaining Todos

• Test full releases:
  • v5.4.0 or a special v6.0.0 (EELS release) 💡
• Test feature releases:
  • BAL 💡 (with EELS) has to wait until this is merged and forks/amsterdam is rebased onto forks/osaka. Not a blocker.
  • Benchmark 💡 (with evmone). Not a blocker. But a quick test to check we can create a feature release with another evm should be required.

How To Create A Fixture Release

• Full release: git tag tests-v6.0.0 && git push upstream v6.0.0
• Feature release: git tag [email protected] && git push upstream [email protected] as an example!

🔗 Related Issues or PRs

N/A

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx --with=tox-uv 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 adding an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).

Cute Animal Picture

[marioevz]

Some comments, and I think we should simply add besu/ethjs back, even if we are not currently using them, we could break their CI or someone else's if they are using it.

[marioevz]

LGTM, thanks!

I think we can merge and setup the token after it has been addressed, do a test release, and then a follow-up PR if anything needs fixing.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.08%. Comparing base (da0c26e) to head (80377f8).
⚠️ Report is 4 commits behind head on forks/osaka.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff              @@
##           forks/osaka    #1608   +/-   ##
============================================
  Coverage        86.08%   86.08%           
============================================
  Files              743      743           
  Lines            44072    44072           
  Branches          3891     3891           
============================================
  Hits             37938    37938           
  Misses            5656     5656           
  Partials           478      478           

Flag	Coverage Δ
unittests	86.08% <ø> (ø)

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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[marioevz]

Just one other comment, thanks!

[danceratopz]

Amazing, thanks @spencer-tb!

Could we rename:

# for consistent extension yml/yaml
git mv .github/actions/build-evm-client/ethjs/action.yml .github/actions/build-evm-client/ethjs/action.yaml

# for more descriptive names
git mv .github/workflows/fixtures.yaml .github/workflows/fixture_full_release.yaml
git mv .github/workflows/fixtures_feature.yaml .github/workflows/fixture_feature_release.yaml

I would love to remove the awk/sed and replace with a Python script similar to .github/scripts/get_release_props.py, but happy to do that as a follow-up!