Update postcss-selector-parser 7.1.0 → 7.1.1 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ postcss-selector-parser (7.1.0 → 7.1.1) · Repo · Changelog

Release Notes

7.1.1

7.1.1

• perf: replace startsWith with strict equality (#308)
• fix(types): add walkUniversal declaration (#311)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

• chore(release): 7.1.1
• fix(types): add `walkUniversal` declaration (#311)
• perf: replace startsWith with strict equality (#308)
• ci: test on Node.js 24 (#307)
• chore: replace abandoned pkg coveralls with coveralls-next
• ci: test on Node.js 22 (#301)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

Walkthrough

The pull request updates a dependency version in the @tailwindcss-upgrade package. Specifically, postcss-selector-parser is bumped from ^7.1.0 to ^7.1.1 in the package.json manifest file. This is a patch-level version increment within the same minor version range. No changes are made to the package's functionality, control flow, or other dependencies. No modifications to exported or public entity declarations are included in this change.

Pre-merge checks

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: a patch version bump of postcss-selector-parser from 7.1.0 to 7.1.1, which directly matches the single file change in the pull request.
Description check	✅ Passed	The description is directly related to the changeset, detailing the postcss-selector-parser update with release notes, commits, and relevant links, though it includes bot-generated boilerplate typical of dependency update PRs.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c8cf8a and 0837efb.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• packages/@tailwindcss-upgrade/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Windows
• GitHub Check: macOS
• GitHub Check: Linux
• GitHub Check: Linux / oxide
• GitHub Check: Linux / cli
• GitHub Check: Linux / webpack
• GitHub Check: Linux / upgrade
• GitHub Check: Linux / vite
• GitHub Check: Linux / postcss

🔇 Additional comments (1)

packages/@tailwindcss-upgrade/package.json (1)

41-41: Patch version bump for postcss-selector-parser is straightforward and safe.

This is a patch-level update (7.1.0 → 7.1.1) within the caret range (^7.1.1), which allows patch updates across the 7.1.x range. The release is valid and consistent with the existing dependency patterns in the file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.