Repository navigation
chore: update dependency lockfile-lint to ^5.1.0 - #779
Merged
Merged
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.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
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.
This PR contains the following updates:
^5.0.1→^5.1.0Release Notes
lirantal/lockfile-lint (lockfile-lint)
v5.1.0Compare Source
Minor Changes
#222
578511e580a4c3c398ba7f26fc0465e449f39516Thanks @deveshsinghal09! - Add opt-in strict SHA-512 integrity validation that detects missing or malformed hashes while allowing Git, local directory, linked workspace and bundled dependencies.Exempt Yarn Classic GitHub codeload archives only when pinned to a full 40-hex
commit. Resolve npm bundled dependencies against their nearest non-bundled
ancestor before flattening: v2/v3 require a non-empty
bundleDependenciesdeclaration and an ancestor with valid SHA-512 integrity or an independent
source exemption. npm v1 verifies the ancestor but cannot confirm the bundle
declaration. Unverified flags and HTTP(S)/local tarball downloads still require
integrity.
Report Yarn Berry as one marked unsupported-format error. The CLI exits non-zero
without calling an unsupported format a security finding; other failing
validators still report their security findings.
Require commit pins for all Git-source exemptions, and recognize percent-encoded
local tarball extensions before granting directory exemptions.
Patch Changes
578511e580a4c3c398ba7f26fc0465e449f39516]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.