Repository navigation
Refresh rank-history catalog and credential permission fixture - #10
Merged
Merged
Conversation
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.
Rank-history responses include format-default metadata, but the offline CLI catalog omitted it. Regenerate the catalog from the corrected shared contract and make the credential-permission refusal fixture explicitly unsafe under restrictive creation masks.
Validation: the canonical source passes 104 affected checks, the complete assembled CLI suite passes 774 with zero failures and one Linux-only skip, and the fresh 209-member 0.6.12 archive passes isolated installation and dependency audit. All 337 copied public source bodies match that qualified canonical package. Version 0.6.12 remains unpublished pending the publisher’s official npm web sign-in.