Fix CI/deploy: realign lockfile and revert breaking Dependabot major bumps - #22
Merged
pedrobritx merged 1 commit intoJul 13, 2026
Conversation
…umps CI and Pages deploy were failing at `npm ci` with: Invalid: lock file's next@16.2.10 does not satisfy next@15.5.20 Three premature Dependabot major bumps had landed together and broke the last-green build (deploy #29274388099): - next 16.2.10 was written into package-lock.json while package.json still declares ^15.5.0, so `npm ci`'s strict check rejected the tree. Regenerating the lockfile pins next back to 15.5.20 (within ^15.5.0). - typescript ^7.0.2 broke `next build`: Next could no longer resolve the tsconfig `@/*` path alias (spurious "Module not found" for @/components/* and @/lib/*) and `tsc --noEmit` errored on CSS side-effect imports. Reverted to ^5.9.3. - tailwindcss ^4.3.2 broke PostCSS: v4 moved the plugin to @tailwindcss/postcss, but the project is written for v3 (@tailwind directives, tailwind.config.ts, tailwindcss in postcss.config). Reverted to ^3.4.19. Full pipeline now green locally: npm ci, typecheck, lint, test (77 passed), and build (static export of all routes to ./out).
pedrobritx
marked this pull request as ready for review
July 13, 2026 22:01
5 tasks
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.
What & why
CI and the GitHub Pages deploy were failing. Both workflows die at the
npm cistep with:Root cause: three premature Dependabot major bumps landed together and broke the last-green build (Pages deploy
#29274388099, the last success before the failures started). This PR realigns the tree with the versions the project is actually written for:next— lockfile only.package-lock.jsoncarriednext@16.2.10whilepackage.jsonstill declares^15.5.0, sonpm ci's strict check rejected the tree. Regenerating the lockfile pinsnextback to15.5.20(within^15.5.0). Nopackage.jsonchange needed here — the merge left the lockfile inconsistent.typescript^7.0.2→^5.9.3. TS 7 brokenext build: Next stopped resolving the tsconfig@/*path alias, producing spuriousModule not founderrors for@/components/*and@/lib/*;tsc --noEmitalso errored on the global CSS side-effect imports. Reverting fixes both.tailwindcss^4.3.2→^3.4.19. Tailwind v4 moved its PostCSS plugin to@tailwindcss/postcssand rejects being used directly. The project is written for v3 (@tailwind base/components/utilities,tailwind.config.ts,tailwindcss: {}inpostcss.config), so v4 failed at CSS processing. Reverting keeps everything consistent with zero code changes.Only
package.json(two devDependencies) andpackage-lock.jsonchange; no application code is touched.How to test
Runs green locally on Node 22; the CI matrix runs the same steps:
Device class unaffected — this is a build/toolchain fix, no runtime/UI change.
Checklist
npm run typecheck,npm run lint,npm test, andnpm run buildpass🤖 Generated with Claude Code
Generated by Claude Code