chore(ci): fix devnet branch format used in release generation#20
Merged
spencer-tb merged 6 commits intoJul 1, 2026
Conversation
The release input validation assumed devnet branches named `<feat>-devnet-<n>`, but execution-specs names them `devnets/<feat>/<n>` (e.g. `devnets/bal/7`, `devnets/glamsterdam/6`). Parse the devnet number from the `devnets/<feat>/<n>` shape and reject branches outside it, and update the error messages, docs, and the `release_fixtures.yaml` branch input hint to match. The `<feat>-devnet` feature name (used for the tag) is unchanged.
Restore the `Fixture Output Directory Structure` section (consensus and benchmark fixture layouts) that the release overhaul removed, placing it below the fixture formats section as requested in review. Tone down the writing in `releases.md` to match the surrounding docs by dropping emdashes in favour of colons and plainer phrasing, removing inline bold emphasis, and keeping bold only for the pinning-guidance labels.
The page conflated a release's name with its git tag. The name `<feature>@vX.Y.Z` (what `consume cache` takes) maps to the git tag and release title `tests-<feature>@vX.Y.Z`, with the `tests` feature as the no-prefix exception (`tests@vX.Y.Z`). Rename the release-types table column from `Tag` to `Release name`, and note in the spec-package admonition that every fixture tag starts with `tests`, the quickest way to tell fixture releases from the bare `vX.Y.Z` package tags.
Add the `blockchain_test_engine_x` fixture format to the formats table, consumed via the `eels/consume-enginex` simulator and located at `./fixtures/blockchain_tests_engine_x/`. It ships in releases because every release feature fills with `--generate-all-formats`.
The release-type bullets lead with the names Tests, Devnet, and Benchmark, which label rows in the release-types table. Quote them so they read as references to those names rather than as plain adjectives.
The "what the workflow produces" list gave `fixtures_<feature>.tar.gz` for every feature, but the `tests` feature builds `fixtures.tar.gz` with no `_tests` in the name, as the example table already shows. Note that exception alongside the parallel tag-naming note.
This was referenced Jul 1, 2026
spencer-tb
merged commit ca14d50
into
spencer-tb:ci/overhaul-fixture-releases
12 of 21 checks passed
danceratopz
added a commit
that referenced
this pull request
Jul 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix-up the devnet branch format used in release generation; few minor docs fixes and tone down the AI style a little :-)
cf