Use version range for PostCSS#20289
Conversation
Confidence Score: 5/5Safe 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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
WalkthroughThe 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
f10d74a to
a32c4b7
Compare
a32c4b7 to
1b0e914
Compare
This PR fixes an issue where new PostCSS release could lead to type related issues if newer versions change the types.
Right now
@tailwindcss/postcssuses a hardcoded PostCSS version. Let's loosen this up and use a semver range instead.Fixes: #20288
Test plan