Hahn-Solo Product Management
  • Dashboard
  • Technologies
  • Competitors
  • Tasks
Theme
Basic Information
Status
Open
Priority
Now
Category
Version Update
Repo
Content SDK PM
Effort
Moderate
Task ID
T-C8D258D2
Details
Upgrade to Next.js 16.2
Complete and merge PR #429 (Next.js 16.2 upgrade). Update peer dependency to include `^16.2.0`. Enable Server Fast Refresh and SRI support in starter templates. Update `create-content-sdk-app` templates to scaffold 16.2-compatible projects.
Why
Next.js 16.2 brings ~400% faster dev startup, Server Fast Refresh, and AI-agent DevTools (AGENTS.md scaffolding, browser log forwarding). These directly complement Content SDK's agent skills story.
Evidence
Next.js 16.2 release (March 18); PR #429 in progress
Details
Context: Next.js 16.2 (March 18, 2026) delivers ~400% faster dev startup via Turbopack improvements, Server Fast Refresh for hot-reloading server code, SRI support, and AI-agent DevTools including AGENTS.md scaffolding and browser-log forwarding. PR #429 is already in progress on the Content SDK repo. This upgrade directly amplifies Content SDK's agent skills value proposition.

Steps:
1. Review and complete PR #429 -- ensure all packages compile and tests pass against Next.js 16.2.1
2. Update `packages/nextjs/package.json` peer dependency to include 16.2.x compatibility
3. Enable Server Fast Refresh in development configuration
4. Update `create-content-sdk-app` Next.js App Router template to target 16.2
5. Document SRI configuration in the starter template's `next.config.ts`
6. Verify Turbopack file system caching still works correctly with Content SDK's build pipeline
7. Test AI-agent DevTools integration with Content SDK's existing AGENTS.md and Skills.md

Acceptance criteria:
All packages build and test against Next.js 16.2.1
`create-content-sdk-app` scaffolds projects targeting Next.js 16.2
Server Fast Refresh works in development mode with Content SDK components
CHANGELOG documents the upgrade

Risks: Next.js 16.2 is a minor release with no breaking changes documented, but Turbopack improvements may surface edge cases in Content SDK's build pipeline. Test thoroughly.
Source Report
reports/product-management/content-sdk/2026-04-05-content-sdk-pm.md
Report date: Apr 5, 2026