Skip to content

Use version range for PostCSS#20289

Merged
RobinMalfait merged 2 commits into
mainfrom
fix/issue-20288
Jun 29, 2026
Merged

Use version range for PostCSS#20289
RobinMalfait merged 2 commits into
mainfrom
fix/issue-20288

Conversation

@RobinMalfait

Copy link
Copy Markdown
Member

This PR fixes an issue where new PostCSS release could lead to type related issues if newer versions change the types.

Right now @tailwindcss/postcss uses a hardcoded PostCSS version. Let's loosen this up and use a semver range instead.

Fixes: #20288

Test plan

  1. All tests still pass

@RobinMalfait RobinMalfait requested a review from a team as a code owner June 29, 2026 13:32
@greptile-apps

greptile-apps Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

Safe to merge — the only change is relaxing an exact PostCSS pin to a compatible range, with no behaviour change for the current development environment.

The change is a one-line edit in the workspace catalog and its corresponding lock file entry. The resolved version in the lock file remains 8.5.15, so nothing changes for local builds or tests. The looser specifier is only visible to consumers of the published package, where it was the source of the reported type errors.

No files require special attention.

Reviews (3): Last reviewed commit: "update changelog" | Re-trigger Greptile

@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: aa02d20b-dc20-48d4-9b8a-bcd94ca3a16b

📥 Commits

Reviewing files that changed from the base of the PR and between c8b081d and 1b0e914.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • CHANGELOG.md
  • pnpm-workspace.yaml

Walkthrough

The postcss catalog entry in pnpm-workspace.yaml is changed from the exact version 8.5.15 to the compatible range ^8.5.15. A corresponding entry is added to CHANGELOG.md under [Unreleased] → Fixed, noting that @tailwindcss/postcss no longer produces type errors with newer PostCSS patch releases.

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the main change: switching PostCSS to a version range.
Description check ✅ Passed The description matches the change and explains the type-error fix with a semver range.
Linked Issues check ✅ Passed The PR updates PostCSS from a pinned version to a caret range, matching issue #20288.
Out of Scope Changes check ✅ Passed The changes are limited to the PostCSS version-range update and a related changelog note.

Comment @coderabbitai help to get the list of available commands.

@RobinMalfait RobinMalfait merged commit 15b4a8c into main Jun 29, 2026
9 checks passed
@RobinMalfait RobinMalfait deleted the fix/issue-20288 branch June 29, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@tailwindcss/postcss: type error when trying to use with latest postcss

1 participant