Skip to content

fix: generating leanSpec test assets#714

Open
shrirajpawar4 wants to merge 1 commit into
leanEthereum:mainfrom
shrirajpawar4:fix/generating-test-aseet
Open

fix: generating leanSpec test assets#714
shrirajpawar4 wants to merge 1 commit into
leanEthereum:mainfrom
shrirajpawar4:fix/generating-test-aseet

Conversation

@shrirajpawar4
Copy link
Copy Markdown
Contributor

Summary

Fixes #711.

Publishes the production fixture bundle from the prod-vectors workflow to a rolling latest GitHub release.

Changes

  • Generate production fixtures with the existing just fill-ci --scheme=prod path.
  • Bundle fixtures/ together with fixtures/keys/prod_scheme.
  • Create release assets:
    • fixtures-prod-scheme.tar.gz
    • fixtures-prod-scheme.tar.gz.sha256
  • Publish both assets to the rolling latest release.
  • Replace the existing latest release/tag on each successful run.
  • Update workflow permissions to contents: write.
  • Add workflow concurrency to avoid racing release replacement.
  • Fix stale poseidon2 cache hash paths to poseidon1.

Notes

The implementation follows the fixture artifact/release pattern used by ethereum/execution-specs, adapted to this repo’s requested rolling latest release model.

Verification

  • Parsed .github/workflows/prod-vectors.yml with Ruby YAML loader.
  • Ran git diff --check.
  • Confirmed no remaining poseidon2 references in prod-vectors.yml.

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.

Add CI which generates leanSpec test assets, and publishes them in leanEthereum/leanSpec release like execution-spec/consensus-spec publish

1 participant