Repository navigation
build(deps): bump postcss-selector-parser from 6.0.16 to 6.1.5 - #1270
Conversation
Bumps [postcss-selector-parser](https://github.com/postcss/postcss-selector-parser) from 6.0.16 to 6.1.5. - [Release notes](https://github.com/postcss/postcss-selector-parser/releases) - [Changelog](https://github.com/postcss/postcss-selector-parser/blob/6.1.5/CHANGELOG.md) - [Commits](postcss/postcss-selector-parser@v6.0.16...6.1.5) --- updated-dependencies: - dependency-name: postcss-selector-parser dependency-version: 6.1.5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying electron-website with
|
| Latest commit: |
95f5b18
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://996e4cc9.electron-website.pages.dev |
| Branch Preview URL: | https://dependabot-npm-and-yarn-post-8ca3.electron-website.pages.dev |
dependabot
Bot
added
the
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
I reviewed this lockfile bump and didn't find any bugs. yarn.lock is covered by the repo-wide CODEOWNERS entry, and the release notes say a new npm publisher released 6.1.5, so a human should still give it a quick look.
What was reviewed:
- 6.1.5 satisfies all four
^6.0.xranges that share this lockfile entry. Its dependencies (cssesc, util-deprecate) are unchanged, and the checksum uses the expected Yarn Berry10c0/format. I could not check the hash against the registry from here. - The separate
^7.0.0entry (yarn.lock:13779) still resolves to 7.0.0. This PR doesn't change it, so I left it out of this review.
Extended reasoning...
The change only touches one yarn.lock entry: the shared postcss-selector-parser 6.x resolution moves from 6.0.16 to 6.1.5 with a new checksum. No package.json or source files change. The package is a build-time CSS tool with no runtime auth or data-handling code, but a new publisher makes this a supply-chain question. I deferred instead of approving because .github/CODEOWNERS assigns * (and so yarn.lock) to a team. The Dependabot notes also say a new releaser published this version, and I couldn't check that or the checksum against the npm registry from this environment.
Bumps postcss-selector-parser from 6.0.16 to 6.1.5.
Release notes
Sourced from postcss-selector-parser's releases.
Changelog
Sourced from postcss-selector-parser's changelog.
Commits
d90b6e36.1.570b0779fix: parse flat selectors in linear time, closing a CPU exhaustion vulnerabil...fb22e126.1.499d9299fix: tolerate non-node children when serializing selectors08ac3e56.1.3bd927e2npm audit fix + update CIb6330e5Improve fix CVE-2026-9358 (NVD) / SNYK-JS-POSTCSSSELECTORPARSER-16873882 (clo...053e949Fix CVE-2026-9358 (NVD) / SNYK-JS-POSTCSSSELECTORPARSER-16873882 (#316)1b1e9c3chore(release): 6.1.2fb38876fix: erroneous trailing combinators in pseudosMaintainer changes
This version was pushed to npm by moox, a new releaser for postcss-selector-parser since your current version.
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.