chore: backport fork changes to upstream - copy #8
Conversation
This file contains 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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
asos-danielc
changed the title
…ty hash when `sha1` is used due to private repositories such as Azure Artifacts not supporting anything other than `sha1`. feat: removed need for `--lockfile` flag if a `yarn.lock` or `package-lock.json` exists. Defaults to `yarn.lock` if not found. You can still specify a lockfile if you wish.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
Fixes #5
Relates to #6
Details
This cherry picks amended commits from the https://github.com/jlp-craigmorten/snyker fork of this repo to contribute changes back, namely:
(as included in the changelog)
This change squashes some patches I have on my fork into a single change against a new v5 version (hence why this change has
5.0.0whereas my fork is currently at5.0.3). Open to suggestion on whether you want to keep the version bump out of this change so you can implement yourselves, or change it as you better suited if disagree with the major.Given the change in Node and NPM version it feels sensible to insist on this being a breaking change.
Also feel free to ignore or edit this change and/or recreate with the pieces you like.