chore: refresh SEP traceability manifest after #295, #303, and #304#305
Merged
Conversation
Regenerated from a full client+server suite run against typescript-sdk@258f1a04a5d3 on current main: - sep-2468: the two new client checks are emitted (tested) and the two authorization-server rows move to excluded (#304) - sep-2243: 12 rows flip to tested now that the custom-header check IDs match their requirements (#303)
Re-ran both suites after rebasing onto main so the manifest also picks up the new sep-2106 block (1 tested, 4 excluded, 3 untracked check IDs emitted by the server scenario with no yaml row yet).
commit: |
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.
Summary
Regenerated
src/seps/traceability.jsonfrom a full client+server suite run againsttypescript-sdk@258f1a04a5d3on currentmain— the same procedure as the scheduled traceability workflow, run manually so the coverage from the three PRs that landed today is reflected without waiting for Monday's run.sep-2468-client-validate-metadata-issuer,sep-2468-client-no-normalization) are now emitted, and the two authorization-server rows are recorded as excluded with their reasons + Add positive tests for the Authorization Code Grant #208 (feat(sep-2468): cover the remaining untested traceability rows #304).sep-2106-anchor-keyword-preserved,sep-2106-composition-keywords-preserved, andsep-2106-conditional-keywords-preserved, which have nocheck:rows insep-2106.yamlyet; they show up underuntracked. That's a follow-up for the SEP-2106 yaml, not something this refresh changes.sourceadvances fromtypescript-sdk@5fc42e9be115totypescript-sdk@258f1a04a5d3.Test plan
node dist/index.js sdk typescript-sdk@main --mode client --suite all -o resultsand--mode server ... --skip-buildproduced 91checks.jsonfilesnode dist/index.js traceability --results results --source typescript-sdk@258f1a04a5d3sourcefield and the SEP-2106 / SEP-2243 / SEP-2468 blocks