chore: bump dependencies to latest within-major#83
Merged
Conversation
date-fns 4.4, i18next 26.3.4, react-i18next 17.0.8, oxlint 1.72, prettier 3.9.4, postcss 8.5.16, autoprefixer 10.5.2. React 19 and Tailwind 4 held back: React 19 breaks the react@18.x peer on @gatsbyjs/reach-router (Gatsby's router); Tailwind 4 needs a dedicated CSS-first config migration. Both warrant their own PRs.
|
Gracias por tu interes en Fullstack Nights y por hacer este Pull Request! Pronto estaremos en contacto. |
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
1 participant
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.
Dependency bumps
Updates all direct dependencies to their latest within-major versions. Lint (
oxlint) andgatsby buildpass clean.Gatsby ecosystem (
gatsby+ plugins) already at latest 5.16.x.Held back (need dedicated PRs)
@gatsbyjs/reach-router@2.0.1(Gatsby's client router) hard-pinsreact@18.x, so React 19 registers as an invalid peer. Gatsby 5.16 does not officially support React 19; shipping it risks client-navigation/hydration breakage the static build won't catch.@themeconfig,@tailwindcss/postcssplugin, built-in content detection replacing@fullhuman/postcss-purgecss). The custom design system intailwind.config.jsmust be ported deliberately.Note on the stuck checks (separate from this PR)
The
percy/WebsiteandMixed content - fullstacknightschecks that hang as "Expected — waiting for status to be reported" are branch-protection required contexts that no integration posts — Percy runs as a CLI step inside thebuildjob, and thebuildjob itself isn't in the required list. That's a repo-settings fix (drop the two phantom contexts, requirebuild), not a code change, so it's not part of this PR.