chore(deps): bump js-yaml, @commitlint/cli and husky - #20
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) to 4.3.1 and updates ancestor dependencies [js-yaml](https://github.com/nodeca/js-yaml), [@commitlint/cli](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli) and [husky](https://github.com/typicode/husky). These dependencies need to be updated together. Updates `js-yaml` from 3.13.1 to 4.3.1 - [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.1/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.13.1...4.3.1) Updates `@commitlint/cli` from 8.3.6 to 21.2.1 - [Release notes](https://github.com/conventional-changelog/commitlint/releases) - [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/cli/CHANGELOG.md) - [Commits](https://github.com/conventional-changelog/commitlint/commits/v21.2.1/@commitlint/cli) Updates `husky` from 2.7.0 to 9.1.7 - [Release notes](https://github.com/typicode/husky/releases) - [Commits](https://github.com/typicode/husky/commits/v9.1.7) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.1 dependency-type: indirect - dependency-name: "@commitlint/cli" dependency-version: 21.2.1 dependency-type: direct:development - dependency-name: husky dependency-version: 9.1.7 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
linkorb-automation
left a comment
linkorb-automation
left a comment
There was a problem hiding this comment.
Security-Reviewed-Head-SHA: 3681f7a
Reviewed head SHA: 3681f7a
Security scope only: this is not a full functional approval.
✅ Security review: thumbs up / no security concerns found
Approved from a security perspective.
This PR only updates JavaScript development tooling and migrates the npm lockfile format. I did not find evidence of new secrets, new package lifecycle scripts, suspicious registry sources, missing lockfile integrity metadata, CI/GitHub Actions privilege changes, or application-code changes affecting authn/authz, injection, XSS/CSRF, SSRF, path traversal, deserialization, crypto/session handling, file upload/download, logging, or tenant isolation.
Notes:
js-yamlis now locked at4.3.1, addressing the old3.13.1dev transitive dependency exposure.- Locked package URLs checked are npm registry HTTPS URLs with integrity fields.
- No install/postinstall/prepare scripts were detected in the v3 lockfile.
- Compatibility note:
@commitlint/cli@21.2.1requires Node>=22.12.0, andhusky@9.1.7requires Node>=18; ensure CI/local tooling uses a compatible Node version.
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.
Bumps js-yaml to 4.3.1 and updates ancestor dependencies js-yaml, @commitlint/cli and husky. These dependencies need to be updated together.
Updates
js-yamlfrom 3.13.1 to 4.3.1Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
86e91b84.3.1 releasedc3cc4b0Backport quadratic complexity fix for !!omap33d05b54.3.0 released663bfabDrop demo publish, to not override new v5 one.1cb8c7bAdd v4-legacy tag for publish02f27afRestore umd builds back to es58be84edFix es5 compatibility59423c6ReplacemaxMergeSeqLengthoption withmaxTotalMergeKeys(more robust). Ba...6842ef6doc polish590dbab4.2.0 releasedUpdates
@commitlint/clifrom 8.3.6 to 21.2.1Release notes
Sourced from @commitlint/cli's releases.
... (truncated)
Changelog
Sourced from @commitlint/cli's changelog.
... (truncated)
Commits
6e20041v21.2.11b4e5bcv21.2.0fdb566ffeat(resolve-extends): resolve pure-ESM presets (conventional-changelog v7/v9...6f1c0afv21.1.07af27bafeat(cli): add --default-config flag to lint without a config file (#4805)51a2d7ftest(cli): verify --cwd redirects config resolution (#997) (#4796)8069048v21.0.2121005efix: disallow same commit hash for --from and --to (#4773)db8d7d6v21.0.11329a25chore: migrate to pnpm (#4762)Updates
huskyfrom 2.7.0 to 9.1.7Release notes
Sourced from husky's releases.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.