Next.js Upgrade Board

• Shifted upgrade triage from repo-by-repo checks to risk- and linkage-driven filtering.
• Enabled execution teams to copy commands straight from the board.

• Consolidated version spread, Vercel linkage, and upgrade commands in one board.
• Generated command templates directly from rule logic.

• Public static snapshot: /projects/nextupgrade/live.html.
• Shows version distribution, project-level detail, and linked/high-risk filters.

• Owner / Product Engineer: defined upgrade rules, built scanning pipelines, and shipped an execution-first board.

• Parallel repositories create fragmented Next.js versions and opaque deployment linkages, making priorities inconsistent.

• Data comes from local repo scans and must stay lightweight for recurring use.
• Output has to be actionable, not merely descriptive.

With many Next.js repos, upgrades become a portfolio problem: which ones are on older majors, which are linked to Vercel, and what should move first.

• Inventory current Next.js versions across repositories.
• Identify linked projects that need stronger production-impact review.
• Generate direct upgrade commands per repository.

• Upgrade summary with project count, version spread, and Vercel linkage.
• Per-project table with path, version, router type, package manager, linkage, and suggested commands.
• Filters for linked projects and higher-risk upgrades.

• Output must be executable, not audit-only.
• Show the version distribution first, then drill into per-project action.
• Keep governance light through a shareable single-page board.

• Scans package.json, lockfiles, and .vercel/project.json for metadata.
• Renders findings as static HTML for sharing, archiving, and reruns.
• Rule layer emits command templates to reduce manual copy mistakes.

• Public site presents a static demo snapshot.
• Live data ingestion remains local, so public output only shows safe snapshots.