{{ message }}
Repository navigation
fix(view): format publisher metadata containing actor information - #10123
Open
sergioperezcheco wants to merge 1 commit into
Open
sergioperezcheco wants to merge 1 commit into
sergioperezcheco wants to merge 1 commit into
Conversation
Assisted-by: Hermes Agent Signed-off-by: sergioperezcheco <checo520@outlook.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.
npm viewformats publisher metadata as a person string, but adding the registry'sactorfield makes the same publisher return an object instead. Recognize actor metadata alongside the existing trusted-publisher case, retaining the three-key limit so unrelated fields are not discarded.Regression tests cover text and JSON output, publisher arrays, and preservation of additional metadata. The root test suite passes with 100% coverage, and root lint passes. Independent public CLI checks against a local registry fixture cover a URL-only publisher and nested actor queries. Workspace-wide and cross-platform release matrices were not run locally.
Prepared and reviewed by autonomous AI agents; no human review is claimed.
References
Fixes #8386