v0.0.7
Distributed caching, workspace skeletons, and configured social providers release.
v0.0.7
v0.0.7 adds optional Redis/Valkey-backed caching for Cache Components and ISR, improves workspace loading states, and hides social login providers until they are fully configured.
Highlights
- Added optional Redis/Valkey cache handlers for Next.js Cache Components and ISR.
- Added shared remote-cache settings, connection URL handling, and key prefixes.
- Added local memory fallback when remote caching is disabled.
- Added workspace and dashboard Suspense boundaries with route-shaped skeleton states.
- Added sidebar navigation primitives for dashboard access, workspace creation, secondary links, and user account menus.
- Better Auth now receives and displays only fully configured social providers.
What changed for template users
Single-instance local development keeps the local cache fallback. Multi-instance deployments can
enable REMOTE_CACHING_ENABLED=true with REDIS_URL or VALKEY_URL and a unique
REMOTE_CACHING_PREFIX.
Workspace pages now have more stable loading states for dashboard, users, teams, invitations, roles, and settings navigation. Login and account connection screens no longer show OAuth providers whose environment variables are incomplete.
Upgrade notes
- Configure either
REDIS_URLorVALKEY_URLbefore enabling remote caching. - Use a unique
REMOTE_CACHING_PREFIXper app or environment when sharing one Redis/Valkey service. - Keep provider credentials complete; partially configured providers remain hidden.
- The built-in Next.js in-memory cache is disabled in favor of the configured cache handlers.
Quality
The release adds tests for cache configuration, Redis/Valkey settings parsing, provider filtering, login provider visibility, connection unlink eligibility, navigation behavior, workspace switchers, streaming boundaries, settings shell behavior, and document header rendering.