Ship the v9 conformance corpus in the relay tarball - #208
Merged
Conversation
The release workflow names the trace fixtures literally, so the v8 -> v9 rename left it copying files that no longer exist and the 0.24.0 tag failed before publishing. ci.yml already moved; this is the same list in the one workflow that had no PR to catch it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
The release workflow names the trace fixtures literally, so the v8 → v9 rename in #207 left it copying files that no longer exist — the
v0.24.0tag failed at Bundle the Pyodide relay assets, before the PyPI publish step (PyPI is still on 0.23.0, so the version is untouched).ci.ymlalready moved in #207;release.ymlis the same list in the one workflow no PR exercises. Re-tagging after this merges.🤖 Generated with Claude Code