Skip to content

build(deps): bump postcss-selector-parser from 6.0.11 to 6.1.5 - #900

Merged
kubeedge-bot merged 1 commit into
masterfrom
dependabot/npm_and_yarn/postcss-selector-parser-6.1.5
Nov 4, 2026
Merged

kubeedge-bot merged 1 commit into
masterfrom
dependabot/npm_and_yarn/postcss-selector-parser-6.1.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Bumps postcss-selector-parser from 6.0.11 to 6.1.5.

Release notes

Sourced from postcss-selector-parser's releases.

6.1.5

The 6.x line is now in security-only maintenance

This release exists because the advisory above covers every published 6.x version, and until now the only remediation on offer was an upgrade to 7.x. 6.1.5 is the patched version for the 6.x line.

The line is kept alive for the installed base that cannot move to 7 yet, Tailwind CSS 3 in particular, which depends on ^6.1.2. From here on it receives security fixes only: no features, no other bug fixes, no type changes. Everything else goes to 7.x, where this package is actively developed. Tailwind CSS 4 no longer depends on this package at all, so this line is expected to retire on its own.

6.1.5 is published under the legacy-v6 npm dist-tag, so npm install postcss-selector-parser keeps resolving to 7.x. Existing ^6 ranges pick up 6.1.5 as usual.

6.1.4

  • fix: tolerate non-node children when serializing selectors

6.1.3

v6.1.2

6.1.2

  • Fixed: erroneous trailing combinators in pseudos

v6.1.1

6.1.1

  • Fixed: improve typings of constructor helpers (#292)

v6.1.0

6.1.0

  • Feature: add sourceIndex to Selector nodes (#290)

v6.0.16

6.0.16

  • Fixed: add missing index argument to each/walk callback types (#289)

v6.0.15

6.0.15

  • Fixed: Node#prev and Node#next type for the first/last node

... (truncated)

Changelog

Sourced from postcss-selector-parser's changelog.

6.1.5 - 2026-10-19

The 6.x line is now in security-only maintenance

This release exists because the advisory above covers every published 6.x version, and until now the only remediation on offer was an upgrade to 7.x. 6.1.5 is the patched version for the 6.x line.

The line is kept alive for the installed base that cannot move to 7 yet, Tailwind CSS 3 in particular, which depends on ^6.1.2. From here on it receives security fixes only: no features, no other bug fixes, no type changes. Everything else goes to 7.x, where this package is actively developed. Tailwind CSS 4 no longer depends on this package at all, so this line is expected to retire on its own.

6.1.5 is published under the legacy-v6 npm dist-tag, so npm install postcss-selector-parser keeps resolving to 7.x. Existing ^6 ranges pick up 6.1.5 as usual.

6.1.4 - 2026-06-11

  • fix: tolerate non-node children when serializing selectors

6.1.3 - 2026-06-11

6.1.2

  • Fixed: erroneous trailing combinators in pseudos

6.1.1

  • Fixed: improve typings of constructor helpers (#292)

6.1.0

  • Feature: add sourceIndex to Selector nodes (#290)

6.0.16

  • Fixed: add missing index argument to each/walk callback types (#289)

6.0.15

  • Fixed: Node#prev and Node#next type for the first/last node

6.0.14

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by moox, a new releaser for postcss-selector-parser since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 3, 2026
@kubeedge-bot kubeedge-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 3, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/postcss-selector-parser-6.1.5 branch 2 times, most recently from b23e45f to e86592d Compare November 4, 2026 07:07
Bumps [postcss-selector-parser](https://github.com/postcss/postcss-selector-parser) from 6.0.11 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.11...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>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/postcss-selector-parser-6.1.5 branch from e86592d to 26749ec Compare November 4, 2026 07:22

@Shelley-BaoYue Shelley-BaoYue left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@kubeedge-bot kubeedge-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 4, 2026
@kubeedge-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Shelley-BaoYue

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubeedge-bot kubeedge-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 4, 2026
@kubeedge-bot
kubeedge-bot merged commit 2b9671b into master Nov 4, 2026
6 of 7 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/postcss-selector-parser-6.1.5 branch November 4, 2026 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants