chore: use public repository metadata URL - #1
Merged
jameslan merged 1 commit intoJun 22, 2026
Merged
Conversation
jameslan
approved these changes
Jun 22, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Jun 22, 2026
…ry metadata URL (#1)"
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.
Summary
Why
The published npm metadata currently resolves the repository to an SSH GitHub URL. A public
git+httpsURL is easier for npm users and automated package tooling to resolve without SSH setup.Validation
npm view typedoc-plugin-version-select@2.0.0 name version repository homepage bugs license --jsonpackage.jsonnpm ci --ignore-scripts --no-audit --no-fundnpm testnpm run buildnpm pack --dry-run --ignore-scripts --json .git diff --check