Bump yaml from 1.10.2 to 1.10.3 in the npm_and_yarn group across 1 directory#530
Bump yaml from 1.10.2 to 1.10.3 in the npm_and_yarn group across 1 directory#530dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [yaml](https://github.com/eemeli/yaml). Updates `yaml` from 1.10.2 to 1.10.3 - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v1.10.2...v1.10.3) --- updated-dependencies: - dependency-name: yaml dependency-version: 1.10.3 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
JiwaniZakir
left a comment
There was a problem hiding this comment.
This is a straightforward dependency bump in pnpm-lock.yaml, updating yaml from 1.10.2 to 1.10.3 across both the packages and snapshots sections. The change is consistent — all three references to the old version (the resolution entry, the cosmiconfig snapshot dependency, and the standalone snapshot) are updated in sync, which is correct.
It's worth verifying what the 1.10.3 patch actually addresses — the yaml changelog notes it fixes a prototype pollution vulnerability (CVE-2021-23341), so this is a security patch rather than a feature bump, and that context is absent from the PR description. Given that yaml is pulled in transitively through cosmiconfig, it would be worth confirming no other transitive consumers in the lockfile still pin to 1.10.2, since a single missed reference could leave the vulnerable version in the resolution graph. A quick grep yaml pnpm-lock.yaml before merging would confirm the lockfile is fully clean.
Bumps the npm_and_yarn group with 1 update in the / directory: yaml.
Updates
yamlfrom 1.10.2 to 1.10.3Commits
cfe8f041.10.37abcf45fix: Catch stack overflow during CST compositiona0252f8chore: Add rules avoiding processing of tests/json-test-suitea5e83b0style: Apply updates Prettier rulesb8ddca0chore: Refresh lockfile395f892ci: Use a different (working) submodule checkout6fd2720test-events: Add {} and [] indicators to flow maps & sequencesDependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.