Repository navigation
chore: sync the protocol fixtures from asobi - #43
Merged
Merged
Conversation
Taure
force-pushed
the
chore/protocol-fixtures
branch
from
August 14, 2026 07:23
edec17f to
73966ea
Compare
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 fixture corpus in
widgrensit/asobichanged, so this brings thevendored copy back in line. Opened by asobi's
protocol-syncworkflow from 22944b98648ba829993e8579ff74c1a76c93b90f.
A new fixture is not automatically dispatched. If this adds an
event this SDK has no case for, the dispatch test will fail and the
case belongs in this PR before it merges.