PR #8: Configurable prompts, shared polling, webpack dev fix

• Repository: msvens/janitor-agent
• Author: msvens
• State: closed | merged: True
• Link: https://github.com/msvens/janitor-agent/pull/8

Description (problem / solution / changelog)

Summary

• Configurable prompts: stored in DB, editable from UI, selectable per-repo
  • 4 prompt types: plan, action, fix, review
  • Default prompts seeded on first startup
  • Prompts page in sidebar (list, create, edit)
  • Per-repo plan/action prompt selection in config page
• Shared StatusProvider: single polling interval replaces multiple independent ones
• Webpack for dev: works around Turbopack Map overflow bug (vercel/next.js#91396)

DB migration

Test plan

• Default prompts appear on first startup
• Prompts page lists all prompts, can edit/create
• Config page shows prompt dropdowns per repo
• Agent uses selected prompt (or default)
• Dev server stable (no Map overflow crash)
• pnpm check passes

Changed files

• package.json (modified, +1/-1)
• src/agent/action.ts (modified, +26/-14)
• src/agent/agent.ts (modified, +3/-1)
• src/agent/planner.ts (modified, +4/-1)
• src/agent/types.ts (modified, +2/-0)
• src/app/api/config/route.ts (modified, +2/-0)
• src/app/api/prompts/[id]/route.ts (added, +39/-0)
• src/app/api/prompts/route.ts (added, +24/-0)
• src/app/config/page.tsx (modified, +45/-1)
• src/app/layout.tsx (modified, +9/-6)
• src/app/prompts/[id]/page.tsx (added, +154/-0)
• src/app/prompts/page.tsx (added, +60/-0)
• src/components/jobs/run-button.tsx (modified, +3/-15)
• src/components/layout/autopilot-banner.tsx (modified, +4/-22)
• src/components/layout/sidebar.tsx (modified, +2/-0)
• src/components/status-provider.tsx (added, +56/-0)
• src/db/index.ts (modified, +112/-0)
• src/db/schema.ts (modified, +16/-1)
• src/db/seed-prompts.ts (added, +108/-0)

---

PR #8: fix: FuzzyText mobile overflow, performance, and infra improvements

• Repository: vpatrin/ccil
• Author: vpatrin
• State: closed | merged: True
• Link: https://github.com/vpatrin/ccil/pull/8

Description (problem / solution / changelog)

Summary

• Fix FuzzyText canvas overflow on mobile with maxWidth: 100% and throttle idle rendering (60fps → 10fps idle, pause when off-screen via IntersectionObserver)
• Throttle Dither shader to ~15fps via frameloop="demand" + invalidate() — visually identical through the dither postprocess, eliminates CPU pinning
• Downgrade Next.js 16.2.3 → 16.1.1 to work around Turbopack pendingOperations memory leak (vercel/next.js#91396)
• Extract all page content into src/content.json for easy editing via GitHub PRs

Changes

Content

• src/content.json — new file, single source of truth for upcoming/past shows and about text
• page.tsx — imports from content.json instead of hardcoded arrays

Performance

• Dither.tsx: frameloop="demand" + setInterval(invalidate, 66) for ~15fps idle rendering, instant invalidate() on pointer move for responsive interaction. Named Three.js imports, removed duplicate DitherProps interface.
• FuzzyText.tsx: IntersectionObserver pauses animation when off-screen, ResizeObserver caches getBoundingClientRect(), idle frame budget raised to 100ms. maxWidth: 100% fixes mobile overflow.

Infrastructure

• /health endpoint + deploy health check verification
• CI: added typecheck job
• CD: SHA-tagged images alongside latest
• Makefile: added dev, build, lint, typecheck, check targets
• docker-compose: healthcheck hits /health instead of /

Cleanup

• Removed Navigation.tsx (unused)
• Updated README, CLAUDE.md, .gitignore
• Phosphor icons import path fix (@phosphor-icons/react instead of deep import)

How to test

1. yarn dev → verify wave background renders, fuzzy text animates
2. Check Activity Monitor — CPU should be near-idle vs previous 100%
3. Scroll down — FuzzyText canvases should pause when off-screen
4. Hover over countdown — interaction should feel responsive
5. Resize browser — no canvas overflow on mobile widths
6. Verify upcoming/past/about sections render correctly from content.json

Changed files

• .claude/commands/health.md (added, +130/-0)
• .claude/settings.json (removed, +0/-8)
• .github/workflows/ci.yml (modified, +14/-0)
• .github/workflows/deploy.yml (modified, +21/-1)
• .gitignore (modified, +1/-0)
• CLAUDE.md (modified, +4/-6)
• Makefile (modified, +15/-1)
• README.md (modified, +70/-21)
• docker-compose.yml (modified, +1/-1)
• package.json (modified, +7/-3)
• src/app/health/route.ts (added, +3/-0)
• src/app/page.tsx (modified, +16/-31)
• src/components/Dither.tsx (modified, +36/-42)
• src/components/FuzzyText.tsx (modified, +31/-9)
• src/components/Navigation.tsx (removed, +0/-14)
• src/content.json (added, +18/-0)
• yarn.lock (modified, +74/-69)

---

PR #9: chore(deps): bump the minor-and-patch group across 1 directory with 5 updates

• Repository: vpatrin/ccil
• Author: dependabot[bot]
• State: closed | merged: False
• Link: https://github.com/vpatrin/ccil/pull/9

Description (problem / solution / changelog)

Bumps the minor-and-patch group with 5 updates in the / directory:

Updates @react-three/fiber from 9.5.0 to 9.6.0

<details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pmndrs/react-three-fiber/releases"><code>@​react-three/fiber</code>'s releases</a>.</em></p> <blockquote> <h2>v9.6.0 - Sunset X</h2> <p>Ever tried using <code>&lt;shaderMaterial uniforms={{ time: { value: time } }} /&gt;</code> and ran into immediate issues with desync? No more.</p> <p>The uniforms objects on <code>ShaderMaterial</code> and its derivatives now have a stable reference. Objects passed into uniforms will instead copy into it. This is the same as behavior for math structures that have copy such as position, rotation, quaternion, etc. and ends up simplifying using the raw JSX where utilities were often introduced before.</p> <p><strong>Why does this matter?</strong></p> <ol> <li> <p>Improves HMR. Even if you memoize the uniforms object it will still regenerate and desync Three. Now this won't happen. But also it makes compatibility with React compiler more complete with its auto-memoization.</p> </li> <li> <p>Allows for inline uniform props and even prop uniforms directly on the material piercing.</p> </li> </ol> <pre lang="js"><code>&lt;shaderMaterial vertexShader={vertexShader} fragmentShader={fragmentShader} // The uniforms object has a stable reference so objects can be safely merged in uniforms={{ uTime: { value: 0 }, uColor: { value: new THREE.Color('hotpink') } }} // Individual uniforms can also be safely updated with pierce notation uniforms-uColor-value={hovered ? 'royalblue' : 'hotpink'} /&gt; </code></pre> <p>Documentation can be found here: <a href="https://r3f.docs.pmnd.rs/api/objects#shader-material-uniforms">https://r3f.docs.pmnd.rs/api/objects#shader-material-uniforms</a></p> <p>And an example can be found here: <a href="https://github.com/pmndrs/react-three-fiber/blob/master/example/src/demos/ShaderMaterial.tsx">https://github.com/pmndrs/react-three-fiber/blob/master/example/src/demos/ShaderMaterial.tsx</a></p> <h2>What's Changed</h2> <ul> <li>fix: Fix broken link on &quot;Performance pitfalls&quot; documentation page by <a href="https://github.com/simonKristensen"><code>@​simonKristensen</code></a> in <a href="https://redirect.github.com/pmndrs/react-three-fiber/pull/3700">pmndrs/react-three-fiber#3700</a></li> <li>fix: uniforms have stable refs for ShaderMaterial by <a href="https://github.com/krispya"><code>@​krispya</code></a> in <a href="https://redirect.github.com/pmndrs/react-three-fiber/pull/3715">pmndrs/react-three-fiber#3715</a></li> <li>docs: fix typos and documentation consistency by <a href="https://github.com/NssGourav"><code>@​NssGourav</code></a> in <a href="https://redirect.github.com/pmndrs/react-three-fiber/pull/3709">pmndrs/react-three-fiber#3709</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/simonKristensen"><code>@​simonKristensen</code></a> made their first contribution in <a href="https://redirect.github.com/pmndrs/react-three-fiber/pull/3700">pmndrs/react-three-fiber#3700</a></li> <li><a href="https://github.com/NssGourav"><code>@​NssGourav</code></a> made their first contribution in <a href="https://redirect.github.com/pmndrs/react-three-fiber/pull/3709">pmndrs/react-three-fiber#3709</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pmndrs/react-three-fiber/compare/v9.5.0...v9.6.0">https://github.com/pmndrs/react-three-fiber/compare/v9.5.0...v9.6.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/877c8392288ca5c237c0ff8e7e1fbd238ade1170"><code>877c839</code></a> chore: Move ShaderMaterial uniform notes to objects out of pitfalls (<a href="https://redirect.github.com/pmndrs/react-three-fiber/issues/3734">#3734</a>)</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/ece1a3fa385ae8687fabae98a25e6656bbca4079"><code>ece1a3f</code></a> RELEASING: Releasing 1 package(s)</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/26e4716412b11a189dd9ac4b3033d0e504f1d7df"><code>26e4716</code></a> docs(changeset): Fix uniforms refs so they remain stable for ShaderMaterial</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/1fb9fcd47ac07ae2b94fe498f68b7b3737fe6b69"><code>1fb9fcd</code></a> docs: fix typos and documentation consistency (<a href="https://redirect.github.com/pmndrs/react-three-fiber/issues/3709">#3709</a>)</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/e1a375c31a89ddaf2ce513c83f88ac5fb2369171"><code>e1a375c</code></a> fix: Uniforms have stable refs for ShaderMaterial (<a href="https://redirect.github.com/pmndrs/react-three-fiber/issues/3715">#3715</a>)</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/582f7871bd5f2107bd62bd83ef5a70f8364d7979"><code>582f787</code></a> docs: fix broken link on &quot;Performance pitfalls&quot; documentation page (<a href="https://redirect.github.com/pmndrs/react-three-fiber/issues/3700">#3700</a>)</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/9525ea0d63c8b42ab6256b82ce068a394f88b1f8"><code>9525ea0</code></a> Update docker_tag in docs.yml workflow</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/56637a21f684d8d18ba8c12e1e01662df69dc041"><code>56637a2</code></a> Upgrade pmndrs/docs workflow to version 3</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/8c9b6564ed7cf78d9cf6a0895e69e89d71faa5ba"><code>8c9b656</code></a> chore: use latest npm in canary</li> <li><a href="https://github.com/pmndrs/react-three-fiber/commit/1bdf70bdae3e5cf14e1efd84507d3d25f908f604"><code>1bdf70b</code></a> chore: copy canary workflow to master</li> <li>Additional commits viewable in <a href="https://github.com/pmndrs/react-three-fiber/compare/v9.5.0...v9.6.0">compare view</a></li> </ul> </details> <br />

Updates next from 16.1.1 to 16.2.3

<details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v16.2.3</h2> <blockquote> <p>[!NOTE] This release is backporting security and bug fixes. For more information about the fixed security vulnerability, please see <a href="https://vercel.com/changelog/summary-of-cve-2026-23869">https://vercel.com/changelog/summary-of-cve-2026-23869</a>. The release does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Ensure app-page reports stale ISR revalidation errors via onRequestError (<a href="https://redirect.github.com/vercel/next.js/issues/92282">#92282</a>)</li> <li>Fix [Bug]: manifest.ts breaks HMR in Next.js 16.2 (<a href="https://redirect.github.com/vercel/next.js/issues/91981">#91981</a> through <a href="https://redirect.github.com/vercel/next.js/issues/92273">#92273</a>)</li> <li>Deduplicate output assets and detect content conflicts on emit (<a href="https://redirect.github.com/vercel/next.js/issues/92292">#92292</a>)</li> <li>Fix styled-jsx race condition: styles lost due to concurrent rendering (<a href="https://redirect.github.com/vercel/next.js/issues/92459">#92459</a>)</li> <li>turbo-tasks-backend: stability fixes for task cancellation and error handling (<a href="https://redirect.github.com/vercel/next.js/issues/92254">#92254</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/icyJoseph"><code>@​icyJoseph</code></a>, <a href="https://github.com/sokra"><code>@​sokra</code></a>, <a href="https://github.com/wbinnssmith"><code>@​wbinnssmith</code></a>, <a href="https://github.com/eps1lon"><code>@​eps1lon</code></a> and <a href="https://github.com/ztanner"><code>@​ztanner</code></a> for helping!</p> <h2>v16.2.2</h2> <blockquote> <p>[!NOTE] This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>backport: Move expanded adapters docs to API reference (<a href="https://redirect.github.com/vercel/next.js/issues/92115">#92115</a>) (<a href="https://redirect.github.com/vercel/next.js/issues/92129">#92129</a>)</li> <li>Backport: TypeScript v6 deprecations for baseUrl and moduleResolution (<a href="https://redirect.github.com/vercel/next.js/issues/92130">#92130</a>)</li> <li>[create-next-app] Skip interactive prompts when CLI flags are provided (<a href="https://redirect.github.com/vercel/next.js/issues/91840">#91840</a>)</li> <li>next.config.js: Accept an option for serverFastRefresh (<a href="https://redirect.github.com/vercel/next.js/issues/91968">#91968</a>)</li> <li>Turbopack: enable server HMR for app route handlers (<a href="https://redirect.github.com/vercel/next.js/issues/91466">#91466</a>)</li> <li>Turbopack: exclude metadata routes from server HMR (<a href="https://redirect.github.com/vercel/next.js/issues/92034">#92034</a>)</li> <li>Fix CI for glibc linux builds</li> <li>Backport: disable bmi2 in qfilter <a href="https://redirect.github.com/vercel/next.js/issues/92177">#92177</a></li> <li>[backport] Fix CSS HMR on Safari (<a href="https://redirect.github.com/vercel/next.js/issues/92174">#92174</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/nextjs-bot"><code>@​nextjs-bot</code></a>, <a href="https://github.com/icyJoseph"><code>@​icyJoseph</code></a>, <a href="https://github.com/ijjk"><code>@​ijjk</code></a>, <a href="https://github.com/gaojude"><code>@​gaojude</code></a>, <a href="https://github.com/wbinnssmith"><code>@​wbinnssmith</code></a>, <a href="https://github.com/lukesandberg"><code>@​lukesandberg</code></a>, and <a href="https://github.com/bgw"><code>@​bgw</code></a> for helping!</p> <h2>v16.2.1</h2> <blockquote> <p>[!NOTE] This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>docs: post release amends (<a href="https://redirect.github.com/vercel/next.js/issues/91715">#91715</a>)</li> <li>docs: fix broken Activity Patterns demo link in preserving UI state guide (<a href="https://redirect.github.com/vercel/next.js/issues/91698">#91698</a>)</li> <li>Fix adapter outputs for dynamic metadata routes (<a href="https://redirect.github.com/vercel/next.js/issues/91680">#91680</a>)</li> <li>Turbopack: fix webpack loader runner layer (<a href="https://redirect.github.com/vercel/next.js/issues/91727">#91727</a>)</li> <li>Fix server actions in standalone mode with <code>cacheComponents</code> (<a href="https://redirect.github.com/vercel/next.js/issues/91711">#91711</a>)</li> <li>turbo-persistence: remove Unmergeable mmap advice (<a href="https://redirect.github.com/vercel/next.js/issues/91713">#91713</a>)</li> <li>Fix layout segment optimization: move app-page imports to server-utility transition (<a href="https://redirect.github.com/vercel/next.js/issues/91701">#91701</a>)</li> <li>Turbopack: lazy require metadata and handle TLA (<a href="https://redirect.github.com/vercel/next.js/issues/91705">#91705</a>)</li> <li>[turbopack] Respect <code>{eval:true}</code> in worker_threads constructors (<a href="https://redirect.github.com/vercel/next.js/issues/91666">#91666</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/d5f649b2f4affdad1009cb178c1e3b37f4f1ad3f"><code>d5f649b</code></a> v16.2.3</li> <li><a href="https://github.com/vercel/next.js/commit/28739286a88a83ab2d4e1899bdb4eb4ee7bee9a9"><code>2873928</code></a> [16.x] Avoid consuming cyclic models multiple times (<a href="https://redirect.github.com/vercel/next.js/issues/75">#75</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/d7c77653602ae2009595cc71eb10f1b8828cc789"><code>d7c7765</code></a> [backport]: Ensure app-page reports stale ISR revalidation errors via onReque...</li> <li><a href="https://github.com/vercel/next.js/commit/c573e8c4f3208711f52bf3b64f5db238c9164762"><code>c573e8c</code></a> fix(server-hmr): metadata routes overwrite page runtime HMR handler (<a href="https://redirect.github.com/vercel/next.js/issues/92273">#92273</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/57b8f659060e1d0f202273a9ed9e56d40f1d1a9c"><code>57b8f65</code></a> next-core: deduplicate output assets and detect content conflicts on emit (<a href="https://redirect.github.com/vercel/next.js/issues/9">#9</a>...</li> <li><a href="https://github.com/vercel/next.js/commit/f158df18bd926d0c2165ad309bbb561d7e73e74a"><code>f158df1</code></a> Fix styled-jsx race condition: styles lost due to concurrent rendering (<a href="https://redirect.github.com/vercel/next.js/issues/92459">#92459</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/356d605b5831ffbe12ce9c9641e5e2e55d203523"><code>356d605</code></a> turbo-tasks-backend: stability fixes for task cancellation and error handling...</li> <li><a href="https://github.com/vercel/next.js/commit/3b77a6e2670ce81d686111b8e466eec612fa1867"><code>3b77a6e</code></a> Fix DashMap read-write self-deadlock in task_cache causing hangs (<a href="https://redirect.github.com/vercel/next.js/issues/92210">#92210</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/b2f208ae98645d119a7e3388ab8a407005619dd8"><code>b2f208a</code></a> Backport: new view-transitions guide, update and fixes (<a href="https://redirect.github.com/vercel/next.js/issues/92264">#92264</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/52faae3d94641584e13691238df5be158d0f00fb"><code>52faae3</code></a> v16.2.2</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v16.1.1...v16.2.3">compare view</a></li> </ul> </details> <br />

Updates react from 19.2.4 to 19.2.5

<details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/releases">react's releases</a>.</em></p> <blockquote> <h2>19.2.5 (April 8th, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Add more cycle protections (<a href="https://redirect.github.com/facebook/react/pull/36236">#36236</a> by <a href="https://github.com/eps1lon"><code>@​eps1lon</code></a> and <a href="https://github.com/unstubbable"><code>@​unstubbable</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/react/commit/23f4f9f30da9e9af2108c18bb197bae75ab584ea"><code>23f4f9f</code></a> 19.2.5</li> <li>See full diff in <a href="https://github.com/facebook/react/commits/v19.2.5/packages/react">compare view</a></li> </ul> </details> <br />

Updates react-dom from 19.2.4 to 19.2.5

<details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/releases">react-dom's releases</a>.</em></p> <blockquote> <h2>19.2.5 (April 8th, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Add more cycle protections (<a href="https://redirect.github.com/facebook/react/pull/36236">#36236</a> by <a href="https://github.com/eps1lon"><code>@​eps1lon</code></a> and <a href="https://github.com/unstubbable"><code>@​unstubbable</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/react/commit/23f4f9f30da9e9af2108c18bb197bae75ab584ea"><code>23f4f9f</code></a> 19.2.5</li> <li>See full diff in <a href="https://github.com/facebook/react/commits/v19.2.5/packages/react-dom">compare view</a></li> </ul> </details> <br />

Updates eslint-config-next from 16.1.1 to 16.2.3

<details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">eslint-config-next's releases</a>.</em></p> <blockquote> <h2>v16.2.3</h2> <blockquote> <p>[!NOTE] This release is backporting security and bug fixes. For more information about the fixed security vulnerability, please see <a href="https://vercel.com/changelog/summary-of-cve-2026-23869">https://vercel.com/changelog/summary-of-cve-2026-23869</a>. The release does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Ensure app-page reports stale ISR revalidation errors via onRequestError (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92282">#92282</a>)</li> <li>Fix [Bug]: manifest.ts breaks HMR in Next.js 16.2 (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91981">#91981</a> through <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92273">#92273</a>)</li> <li>Deduplicate output assets and detect content conflicts on emit (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92292">#92292</a>)</li> <li>Fix styled-jsx race condition: styles lost due to concurrent rendering (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92459">#92459</a>)</li> <li>turbo-tasks-backend: stability fixes for task cancellation and error handling (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92254">#92254</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/icyJoseph"><code>@​icyJoseph</code></a>, <a href="https://github.com/sokra"><code>@​sokra</code></a>, <a href="https://github.com/wbinnssmith"><code>@​wbinnssmith</code></a>, <a href="https://github.com/eps1lon"><code>@​eps1lon</code></a> and <a href="https://github.com/ztanner"><code>@​ztanner</code></a> for helping!</p> <h2>v16.2.2</h2> <blockquote> <p>[!NOTE] This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>backport: Move expanded adapters docs to API reference (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92115">#92115</a>) (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92129">#92129</a>)</li> <li>Backport: TypeScript v6 deprecations for baseUrl and moduleResolution (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92130">#92130</a>)</li> <li>[create-next-app] Skip interactive prompts when CLI flags are provided (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91840">#91840</a>)</li> <li>next.config.js: Accept an option for serverFastRefresh (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91968">#91968</a>)</li> <li>Turbopack: enable server HMR for app route handlers (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91466">#91466</a>)</li> <li>Turbopack: exclude metadata routes from server HMR (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92034">#92034</a>)</li> <li>Fix CI for glibc linux builds</li> <li>Backport: disable bmi2 in qfilter <a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92177">#92177</a></li> <li>[backport] Fix CSS HMR on Safari (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/92174">#92174</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/nextjs-bot"><code>@​nextjs-bot</code></a>, <a href="https://github.com/icyJoseph"><code>@​icyJoseph</code></a>, <a href="https://github.com/ijjk"><code>@​ijjk</code></a>, <a href="https://github.com/gaojude"><code>@​gaojude</code></a>, <a href="https://github.com/wbinnssmith"><code>@​wbinnssmith</code></a>, <a href="https://github.com/lukesandberg"><code>@​lukesandberg</code></a>, and <a href="https://github.com/bgw"><code>@​bgw</code></a> for helping!</p> <h2>v16.2.1</h2> <blockquote> <p>[!NOTE] This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>docs: post release amends (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91715">#91715</a>)</li> <li>docs: fix broken Activity Patterns demo link in preserving UI state guide (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91698">#91698</a>)</li> <li>Fix adapter outputs for dynamic metadata routes (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91680">#91680</a>)</li> <li>Turbopack: fix webpack loader runner layer (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91727">#91727</a>)</li> <li>Fix server actions in standalone mode with <code>cacheComponents</code> (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91711">#91711</a>)</li> <li>turbo-persistence: remove Unmergeable mmap advice (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91713">#91713</a>)</li> <li>Fix layout segment optimization: move app-page imports to server-utility transition (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91701">#91701</a>)</li> <li>Turbopack: lazy require metadata and handle TLA (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91705">#91705</a>)</li> <li>[turbopack] Respect <code>{eval:true}</code> in worker_threads constructors (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/91666">#91666</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/d5f649b2f4affdad1009cb178c1e3b37f4f1ad3f"><code>d5f649b</code></a> v16.2.3</li> <li><a href="https://github.com/vercel/next.js/commit/52faae3d94641584e13691238df5be158d0f00fb"><code>52faae3</code></a> v16.2.2</li> <li><a href="https://github.com/vercel/next.js/commit/ed7d2cef246dcb3e2955c018fd8b2027e0ff8eed"><code>ed7d2ce</code></a> v16.2.1</li> <li><a href="https://github.com/vercel/next.js/commit/c5c94dffbf084e66b172a9c6ff23d80c24973764"><code>c5c94df</code></a> v16.2.0</li> <li><a href="https://github.com/vercel/next.js/commit/3683192a6bea9011222e9b236f8000b5266f3fe6"><code>3683192</code></a> v16.2.0-canary.104</li> <li><a href="https://github.com/vercel/next.js/commit/668981482a3f9de97c4c1371e940e0f84972c080"><code>6689814</code></a> v16.2.0-canary.103</li> <li><a href="https://github.com/vercel/next.js/commit/ad66dbc89b356867c308110dc5365a696c763991"><code>ad66dbc</code></a> v16.2.0-canary.102</li> <li><a href="https://github.com/vercel/next.js/commit/b8564984305ff0f4feb9e7f709652a735b89aa0a"><code>b856498</code></a> v16.2.0-canary.101</li> <li><a href="https://github.com/vercel/next.js/commit/136b77e4d971de868b56066e714c1f187af6cb23"><code>136b77e</code></a> v16.2.0-canary.100</li> <li><a href="https://github.com/vercel/next.js/commit/0f599731b86e177508c9d28af7414e9d94a01193"><code>0f59973</code></a> v16.2.0-canary.99</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/commits/v16.2.3/packages/eslint-config-next">compare view</a></li> </ul> </details> <br />

Changed files

• package.json (modified, +5/-5)
• yarn.lock (modified, +81/-86)