build(deps): bump postcss, @next/third-parties and next - #3054
build(deps): bump postcss, @next/third-parties and next#3054dependabot[bot] wants to merge 2 commits into
Conversation
dependabot
Bot
added
dependencies
|
@juliusv mind taking a peek at this? |
Bumps [postcss](https://github.com/postcss/postcss), [@next/third-parties](https://github.com/vercel/next.js/tree/HEAD/packages/third-parties) and [next](https://github.com/vercel/next.js). These dependencies needed to be updated together. Updates `postcss` from 8.5.18 to 8.5.23 - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.5.18...8.5.23) Updates `@next/third-parties` from 15.3.2 to 16.3.0 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.3.0/packages/third-parties) Updates `next` from 15.5.22 to 16.3.0 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v15.5.22...v16.3.0) --- updated-dependencies: - dependency-name: postcss dependency-version: 8.5.23 dependency-type: direct:development - dependency-name: "@next/third-parties" dependency-version: 16.3.0 dependency-type: direct:production - dependency-name: next dependency-version: 16.3.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Next.js 16 / React 19 no longer allow passing a component (a function)
as a prop from a Server Component to a Client Component. The Mantine
`component={Link}` / `component={NextImage}` polymorphic pattern was used
in several Server Components, which broke the static export build with
"Functions cannot be passed directly to Client Components".
Introduce small Client Component wrappers (LinkAnchor, LinkButton,
LinkCard, NextMantineImage) that bake in the function-valued `component`
prop, and use them from the affected pages/components so those can stay
Server Components.
Assisted-by: opencode (claude-opus-4-8)
Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
bca0e43 to
cd98e18
Compare
sysadmind
left a comment
sysadmind
left a comment
There was a problem hiding this comment.
next v16 removed the next lint command which is still defined in package.json. https://nextjs.org/blog/next-16#breaking-changes-and-other-updates This also means that next build doesn't run the lint anymore - we lose that built in. The recommendation is to run eslint directly or switch to biome. I think biome might be a good idea. Alertmanager already made the switch.
One UI bug I see in the upgrade - smooth scrolling is broken. If you look at the preview site under docs - select a long page and scroll down. While scrolled, select a different nav item. It will visually scroll back up to just below the title. This is different from the current site in 2 ways: 1) the current site immediately jumps to the top 2) the jump is to a position that includes the title.
Before:
After:
V16 also requires Node 20.9, but I don't see where we set the version anywhere. We've taken to using nvmrc in Prometheus and Alertmanager. I don't know how it works with Netlify. I don't see much CI/CD in this repo itself which might be a good addition in itself. https://nextjs.org/blog/next-16#breaking-changes-and-other-updates
3 participants
Bumps postcss, @next/third-parties and next. These dependencies needed to be updated together.
Updates
postcssfrom 8.5.18 to 8.5.23Release notes
Sourced from postcss's releases.
Changelog
Sourced from postcss's changelog.
Commits
eb9e1feRelease 8.5.23 version9d19c78Update dependencies7beca13Does no load source map file without opts.fromdecea51Typoc18e30dUpdate EM banner98a39adUpdate EM bannera3e48c4Release 8.5.22 versionf49d691Fix custom property losing its semicolon before a comment (#2117)28e0dafRelease 8.5.21 version3d2b4e4Update dependenciesUpdates
@next/third-partiesfrom 15.3.2 to 16.3.0Release notes
Sourced from @next/third-parties's releases.
... (truncated)
Commits
d73f562v16.3.04fd843fv16.3.0-canary.1079480f7fv16.3.0-canary.106a8dcd25v16.3.0-canary.10538f0cdev16.3.0-canary.104f3edea1v16.3.0-canary.1030d5ff0dv16.3.0-canary.102cf1e001v16.3.0-canary.101267d6b1v16.3.0-canary.100ad618bfRestore canary version 16.3.0-canary.99 after v16.3.0-preview.10 preview releaseMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@next/third-partiessince your current version.Updates
nextfrom 15.5.22 to 16.3.0Release notes
Sourced from next's releases.
... (truncated)
Commits
d73f562v16.3.02e0d4cbEdits to turbopackFileSystemCache (#96531)86df9c7docs: cover direct visits and client navigations in the instant() e2e example...47a52c0[turbopack / next.js] Add an end-to-end test for new root detection (#96544)8e878d4Remove implicit Partial Prefetching opt-in frominstant(#96539)e37ddd1Fix deploy test TypeScript exclusions (#96545)8a4920cdocs: clarify first-party Skills workflows (#96495)4344b83Flag newly disabled deploy tests (#96505)459617afix: double fragment on navigation (#93132)cbf0cefEnable TypeScript CLI by default (#96497)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.