ci: expose extension conformance gaps#1019
Merged
Merged
Conversation
github-actions
Bot
added
T-documentation
DaleSeo
force-pushed
the
ci/extension-conformance-visibility
branch
from
July 21, 2026 13:40
9027e9c to
0d52113
Compare
DaleSeo
marked this pull request as ready for review
July 21, 2026 13:41
alexhancock
previously approved these changes
Jul 21, 2026
alexhancock
left a comment
alexhancock
left a comment
Contributor
There was a problem hiding this comment.
LGTM other than conflicts
DaleSeo
force-pushed
the
ci/extension-conformance-visibility
branch
from
July 21, 2026 13:57
0d52113 to
2638141
Compare
alexhancock
self-requested a review
July 21, 2026 14:14
alexhancock
approved these changes
Jul 21, 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.
Motivation and Context
This separates tier-scored dated protocol conformance from informational extension coverage, which was previously filtered out by
--spec-version. CI now runs the SEP-2663 Tasks and client extension scenarios under a strict extension-specific expected-failures baseline, so new failures and stale exemptions fail the build. The roadmap reports current dated-suite pass rates and extension gaps independently.How Has This Been Tested?
Breaking Changes
None.
Types of changes
Checklist