Hold Tailwind at v3: revert root bump from #51, ignore v4 majors in Dependabot - #55
Merged
Merged
Conversation
PR #51 bumped the root tailwindcss devDependency to 4.3.0. CI stayed green only because nothing CI runs uses the root Tailwind install — but the theme's tailwind.config.js and PostCSS pipeline are v3, so the *-tw scripts were left broken. Revert to ^3.4.0. PR #52 fails E2E for the same reason one level down: its group bump takes exampleSite's tailwindcss to 4.3.0, whose PostCSS plugin moved to @tailwindcss/postcss, so postcss.config.js errors and hugo server never starts. Add Dependabot ignore rules for tailwindcss major updates in both npm ecosystems so the group PR can be recreated without the v4 bump. Tailwind v4 migration is a deliberate future change, tracked separately from the v0.3 spec (#53). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VRxJsK91SRR9AMxwJvhrqq
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
2 participants
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.
Phase D of the v0.3 plan (#53): unblocks Dependabot PR #52.
What
tailwindcssto^3.4.0(lockfile resolves 3.4.19). Bump the npm-dev-dependencies group across 1 directory with 5 updates #51 bumped it to 4.3.0; CI stayed green only because nothing CI runs touches the root Tailwind install, but the theme'stailwind.config.jsand PostCSS pipeline are v3, so the*-twscripts were silently broken.ignorerules fortailwindcssmajor updates in both npm ecosystems (root and/exampleSite).Why
#52's E2E failure is Tailwind v4 in the
exampleSitegroup bump: v4 moved its PostCSS plugin to@tailwindcss/postcss, sopostcss.config.jserrors andhugo servernever starts — every E2E test fails at webserver startup. The theme is built on v3; a v4 migration is a deliberate future project, separate from the v0.3 spec.After merge
Comment
·@·d·ependabot r·ecreateon #52 so it regenerates without the v4 bump (Dependabot reads this config from the default branch). The Font Awesome 6→7 major stays in the group — fresh CI on the recreated PR will tell us whether it's safe.🤖 Generated with Claude Code
https://claude.ai/code/session_01VRxJsK91SRR9AMxwJvhrqq
Generated by Claude Code