import { IMPOSSIBLE, VersionInfo } from '@start9labs/start-sdk'

/**
 * v1.2.0:1 — Next.js 14 -> 15 / React 18 -> 19 upgrade (2026-06-13).
 *
 * The remaining P1 from the full-eval queue: move off Next.js 14 onto the
 * CVE-patched Next 15 line (15.5.x), closing the framework's RSC
 * DoS/source-exposure advisories and the middleware-auth-bypass class that
 * applied to the 14.x `middleware.ts` auth gate. App Router on Next 15
 * requires React 19, so react/react-dom move to 19.x in lockstep
 * (lucide-react + next-themes bumped to their React-19-compatible releases).
 *
 * Code surface was the Next 15 async-request-API change: `params` and
 * `searchParams` are now Promises. All `[id]` route handlers (10 files) and
 * the four server pages that read them now `await` the resolved value;
 * `cookies()`/`headers()` were already awaited from the earlier auth work, so
 * no other request-API changes were needed. All routes remain dynamic, so the
 * Next 15 "uncached by default" change is a no-op here. next.config.js (static
 * CSP) and the middleware matcher are unchanged.
 *
 * App-code + dependency upgrade only — no schema, no API contract change, no
 * data migration. Existing /data survives untouched.
 */
export const v_1_2_0_1 = VersionInfo.of({
  version: '1.2.0:1',
  releaseNotes: {
    en_US:
      'Platform upgrade: the app now runs on Next.js 15 and React 19, picking up the framework security patches and a more current runtime. No new features and no data changes — this is a maintenance release, and your existing data is untouched.',
  },
  migrations: {
    up: async () => {},
    down: IMPOSSIBLE,
  },
})