feat: override pnpm audit registry parameter#8158
Merged
jeremylong merged 1 commit intodependency-check:mainfrom Dec 2, 2025
Merged
feat: override pnpm audit registry parameter#8158jeremylong merged 1 commit intodependency-check:mainfrom
jeremylong merged 1 commit intodependency-check:mainfrom
Conversation
jeremylong
approved these changes
Nov 30, 2025
Collaborator
|
Additional changes will be needed to expose to cli, plugins etc (via their native config) and their docs I guess. |
Collaborator
|
@chadlwilson if someone wants to expose these they can submit a PR. It is possible to override the default now using the properties mechanisms built into the various integrations. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Description of Change
Allows overriding the value of the --registry parameter that is passed to pnpm audit.
The current behavior always goes to https://registry.npmjs.org/ which is not always allowed.
Related issues
Have test cases been added to cover the new functionality?
no