ci: per-file companion repo mapping for schema cross-check - #587
Merged
Conversation
SbeB3UmdfConsumer is a dead/renamed name for B3MarketDataPlatform (GitHub silently redirects it), which happened to still work here since this repo is genuinely independent of B3MarketDataPlatform, but relying on a rename-redirect for a security-relevant check is fragile (the name could later be reclaimed by an unrelated repo). This repo vendors two schema files with two different companions, so map by filename instead of hardcoding one target: b3-market-data-messages-*.xml -> B3MarketDataPlatform b3-entrypoint-messages-*.xml -> B3EntryPointClient An unrecognized filename only warns, same fail-open-on-unknown behavior as a fetch failure. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
SbeB3UmdfConsumer is a dead/renamed name (now B3MarketDataPlatform); replace all remaining doc/code/config references with the correct current repo names (B3MarketDataPlatform for the UMDF/market-data consumer, B3EntryPointClient for the entrypoint client), consistent with the ci.yml companion-repo fix in this branch. Also fixes an unrelated stale build command in docs/EXCHANGE-SIMULATOR.md that referenced a solution file (SbeB3UmdfConsumer.slnx) that has never existed in this repo; the real file is SbeB3Exchange.slnx. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pedrosakuma
added a commit
that referenced
this pull request
Jul 27, 2026
…eference schema-guard CI - Merge main into docs/protocol-contract-gate to pick up the SbeB3UmdfConsumer cleanup from #587 (this PR branched before that merge and had reintroduced the stale companion-repo name in CONTRIBUTING.md and copilot-instructions.md). - Add a note in CONTRIBUTING.md's 'Schemas are vendored' and 'Protocol contract evidence gate' sections, and in copilot-instructions.md, pointing to the Vendored schema guard CI job as the deterministic backstop, since the new issue forms/PR checklist are review-time discipline only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
1 participant
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.
Fixes the same
SbeB3UmdfConsumerdead-name issue found in B3MarketDataPlatform (that name is a renamed alias for B3MarketDataPlatform, so relying on it is fragile even though it happened to redirect to a genuinely independent repo here).This repo vendors two schema files with two different real companions, so cross-check by filename instead of one hardcoded target:
b3-market-data-messages-*.xml->B3MarketDataPlatformb3-entrypoint-messages-*.xml->B3EntryPointClientAn unrecognized filename only warns (same fail-open-on-unknown behavior as a fetch failure).