Repository navigation
deps: Bump postcss-selector-parser and tailwindcss in /site/homepage - #190
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Removes [postcss-selector-parser](https://github.com/postcss/postcss-selector-parser). It's no longer used after updating ancestor dependency [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss). These dependencies need to be updated together. Removes `postcss-selector-parser` Updates `tailwindcss` from 3.4.19 to 4.3.3 - [Release notes](https://github.com/tailwindlabs/tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.3/packages/tailwindcss) --- updated-dependencies: - dependency-name: postcss-selector-parser dependency-version: dependency-type: indirect - dependency-name: tailwindcss dependency-version: 4.3.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/site/homepage/multi-d49ef80a9c
branch
from
October 20, 2026 16:28
e0bcf8c to
005bb34
Compare
nicolasbisurgi
added a commit
that referenced
this pull request
Oct 26, 2026
Since #183 every homepage major arrives as its own PR. That broke React: the 19 major came in as a react-dom-only PR (#201) that bumped @types/react-dom without @types/react, so `npm ci` failed on the peer dependency. react, react-dom and their types have to move together, so React majors now get their own group, listed ahead of the homepage group so minors and patches still fall through to it. tailwindcss 4 (#190) and lucide-react 1 (#200) both need real migrations -- Tailwind's PostCSS plugin moved to @tailwindcss/postcss, and lucide 1 dropped the brand icons, including `Github`, which three homepage components import. Their majors are ignored until those migrations are scheduled, so Dependabot stops reopening failing PRs for them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/site/homepage/multi-d49ef80a9c
branch
October 26, 2026 20:47
nicolasbisurgi
added a commit
that referenced
this pull request
Oct 26, 2026
…203) Since #183 every homepage major arrives as its own PR. That broke React: the 19 major came in as a react-dom-only PR (#201) that bumped @types/react-dom without @types/react, so `npm ci` failed on the peer dependency. react, react-dom and their types have to move together, so React majors now get their own group, listed ahead of the homepage group so minors and patches still fall through to it. tailwindcss 4 (#190) and lucide-react 1 (#200) both need real migrations -- Tailwind's PostCSS plugin moved to @tailwindcss/postcss, and lucide 1 dropped the brand icons, including `Github`, which three homepage components import. Their majors are ignored until those migrations are scheduled, so Dependabot stops reopening failing PRs for them. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Removes postcss-selector-parser. It's no longer used after updating ancestor dependency tailwindcss. These dependencies need to be updated together.
Removes
postcss-selector-parserUpdates
tailwindcssfrom 3.4.19 to 4.3.3Release notes
Sourced from tailwindcss's releases.
... (truncated)
Changelog
Sourced from tailwindcss's changelog.
... (truncated)
Commits
c2b24dd4.3.3 (#20334)e48c5e8Fix weird character rendering on Windows with Japanese locale (#20318)35a3e9cAlways produce\<length>value when optimizing--spacing(0)(#20319)4af47fbFix hues in achromatic theme colors to benone(#20314)5835691Handle CSS nesting natively (#20124)67c745eFix bug in attribute selector parsing (#20303)2683903Support fractional opacity modifiers for named shadow sizes (#20302)04588b1Fix theme() in JS plugins returning unresolved object instead of DEFAULT valu...b53fa09fix: exclude iframes from focus-visible auto outline in Preflight (#20292)ef79119Bump dependencies (#20300)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for tailwindcss since your current version.