fixes for next 16 - #433
Merged
Merged
Conversation
Signed-off-by: Peter Jausovec <peter.jausovec@solo.io>
kristin-kronstain-brown
approved these changes
Aug 5, 2026
Contributor
|
@peterj If you're ready want to merge yours? I'll pull those changes into my PR then. |
Contributor
Author
|
done! |
kristin-kronstain-brown
added a commit
that referenced
this pull request
Aug 5, 2026
Takes main's Next 16 migration (#433) over this branch's Next 15 hold. Git auto-merged @next/mdx and @next/third-parties to ^16.3.0 (main's side) while keeping next at ^15.5.21 (this branch's side) — a silent peer-dep conflict. Resolved next to ^16.3.0 so the three move together. Kept this branch's security hardening, which main does not have: - postcss floor ^8.5.23 (was ^8) - overrides: postcss ^8.5.23, sharp ^0.35.0 The sharp override still does work under Next 16: next@16.3.0 declares sharp ^0.35.3, but main's lock also carries a vulnerable sharp@0.34.5. With the override the tree resolves to a single sharp@0.35.3. public/sitemap.xml conflict resolved to main's copy (generated at build). Verified: npm ci (root + docs-site) exit 0; make build exit 0 on Next 16 Turbopack, 234 Hugo pages, OpenNext worker built; npm audit clean for next, postcss, and sharp; docs-site/content hand edits byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Kristin Brown <kristin.brown@solo.io>
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.
No description provided.