fix: resolve cacheComponents build error with @clerk/nextjs canary

[jacekradko]

Summary

This PR demonstrates that the build error reported in clerk/javascript#7913 is resolved by the fix in clerk/javascript#7989.

The problem: next build with cacheComponents: true and a dynamic route (/test-route/[id]) failed with:

Error: Route "/test-route/[id]": Uncached data or `connection()` was accessed outside of `<Suspense>`.

The fix: @clerk/nextjs@7.0.2-canary.v20260305143125 removes usePathname from the internal navigation hook when cacheComponents is enabled, which was the source of the dynamic data access outside Suspense.

Changes

• Updated @clerk/nextjs to 7.0.2-canary.v20260305143125 (includes the fix)
• Updated header.tsx to use the v7 Show component API (SignedIn/SignedOut → Show)

Build output

▲ Next.js 16.1.6 (Turbopack, Cache Components)

Route (app)
┌ ○ /
├ ○ /_not-found
├ ○ /test-route
└ ◐ /test-route/[id]

○  (Static)             prerendered as static content
◐  (Partial Prerender)  prerendered as static HTML with dynamic server-streamed content

The dynamic route /test-route/[id] now correctly renders as Partial Prerender instead of failing the build.

[Pmacdon15]

Thanks so much