chore(deps): bump next from 16.0.1 to 16.0.3 #10
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove [locale] directory structure, move pages to app root - Remove S3 configuration from .env (API returns complete URLs) - Update proxy.ts to use single locale with never prefix - Update layout.tsx to read locale from config - Add NEXT_PUBLIC_LOCALE env variable support - Fix 404 error on root path (/) - Site now accessible without locale prefix 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Remove withNextIntl plugin from next.config.ts - Remove proxy.ts and middleware.ts (not needed for single locale) - Create simple messages system in src/lib/i18n/messages.ts - Remove NextIntlClientProvider and use messages directly - Fetch team information from /v1/teams/ API in layout - Display site name from API instead of env variable - Remove S3 variables from .env.local (API returns complete URLs) - Site now works without locale prefix at root path Fixes: - 404 error on http://localhost:3000/ resolved - Site name now comes from Rush CMS API - No dependency on S3 configuration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- create SiteContext to share site info globally - update Navigation to display site name from API - convert HomePage to client component to use context - site name now shown in navbar, homepage and footer
- convert static metadata export to generateMetadata function - fetch team data to get site name for title - title now shows site name from API instead of env variable
- add getSiteName helper function to fetch team name - update metadata helpers to accept optional siteName parameter - convert blog and contact pages to use generateMetadata - all page titles now use template: "Page Title | Site Name" - site name comes from API instead of env variables
- fix navigation component key prop warnings by restructuring render - skip environment validation on client-side (browser context) - all keys now properly assigned in navigation items and children
- convert page.tsx from client to server component to access API_TOKEN - create HomeHero client component for dynamic site name display - simplify NavigationItems to fix React key prop warnings - remove recursive rendering in favor of inline mapping
- Update RushCMSImage type with thumb/preview fields - Add featured_image field to RushCMSEntry - Create comprehensive block type definitions (13 block types) - Add API functions: getEntriesByCollection, getEntryByCollectionAndSlug - Remove collection IDs from config (BLOG_COLLECTION_ID, PAGES_COLLECTION_ID) - Collections now fetched dynamically via slug instead of hardcoded IDs This enables collection-agnostic routing and block rendering system. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Add block types and BlockRendererProps interface - Create UnknownBlock component with graceful degradation * Shows warning in development with block type and data * Returns null in production (zero visual impact) * Logs console warning for developers - Create BlockRenderers map and getBlockRenderer helper - Add placeholder comments for all 13 block types Foundation ready for implementing individual block components. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Implemented all block components: - Basic: richtext, quote, callout, toggle, paragraph - Media: image, gallery, video - Embed: youtube, embed, bookmark - Advanced: alert, divider, code, columns, button - Updated block type definitions with all required fields - Fixed type errors in richtext (JSX heading tags) and columns (nested rendering) - Registered all blocks in BlockRenderers map - Added graceful degradation with UnknownBlock fallback 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Created dynamic routing infrastructure: - [collectionSlug]/page.tsx - Collection archive pages with automatic generation - [collectionSlug]/[entrySlug]/page.tsx - Single entry pages with nested routing - BlockRenderer component - Unified block rendering across all entry types Updated existing routes to use new API: - blog/page.tsx - Now uses getEntriesByCollection - blog/[slug]/page.tsx - Uses getEntryByCollectionAndSlug - [slug]/page.tsx (pages) - Uses getEntryByCollectionAndSlug - page.tsx (homepage) - Uses getEntriesByCollection - sitemap.ts - Uses getEntriesByCollection Enhanced Article component: - Added BlockRenderer integration for full block system support - Added featured_image display with Next.js Image optimization - Improved metadata with featured image URL support All routes now work with collection slugs instead of hardcoded IDs, enabling fully dynamic multi-collection websites. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Created fully dynamic homepage system: - CollectionSection component with collection-specific icons and styling - Automatic collection detection and entry fetching - Smart icon mapping for common collection types (blog, news, events, team, projects, gallery) - "View All" links for each collection - Empty state handling (only shows collections with entries) Updated BlogCard component: - Added basePath prop for collection-agnostic routing - Now works with any collection (blog, news, products, etc.) - Maintains backward compatibility with default /blog path Homepage enhancements: - Fetches all collections dynamically using getCollections() - Displays up to 3 latest entries per collection - Responsive grid layout (1/2/3 columns) - Alternating section backgrounds for visual separation - Collection descriptions from API - Error handling for individual collection failures The homepage now automatically adapts to any number of collections without code changes, making it truly collection-agnostic. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Renamed blog-card.tsx to entry-card.tsx - Updated interface from BlogCardProps to EntryCardProps - Updated component function from BlogCard to EntryCard - Changed type from BlogEntry to RushCMSEntry for full generality - Updated all imports across codebase: - blog/blog-listing.tsx - home/collection-section.tsx - blog/tag/[slug]/page.tsx This makes the component more semantically appropriate for use across all collection types, not just blog posts. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…error
Removed src/app/[slug]/page.tsx which was causing a conflict with
[collectionSlug] route. Both routes were at the same level, causing
Next.js to throw: "You cannot use different slug names for the same
dynamic path ('collectionSlug' !== 'slug')".
The [slug] route was only serving the 'pages' collection, which is
now fully covered by the dynamic [collectionSlug]/[entrySlug] routing
system. Pages from the 'pages' collection can now be accessed via
/pages/slug instead of /slug.
This completes the transition to a fully collection-agnostic routing
architecture.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
…pattern Implements clean URLs for institutional pages while maintaining collection-agnostic architecture. Collections and root entries now share the same [slug] route with intelligent fallback logic. Changes: - Added ROOT_COLLECTION_SLUG env var (optional, defaults to 'pages') - Added config.routing.rootCollectionSlug configuration - Merged [collectionSlug] into unified [slug] route pattern - [slug]/page.tsx: Checks if slug is collection first, then root entry - [slug]/[entrySlug]/page.tsx: Handles all collection entries - Removed conflicting [collectionSlug] routes entirely URL Structure: - / → Homepage - /about → Entry from root collection (pages) - /blog → Collection archive - /blog/post-1 → Entry from blog collection Routing Priority: 1. Collection match (if slug matches collection) 2. Root collection entry (if ROOT_COLLECTION_SLUG set) 3. 404 (if neither match) This resolves Next.js "different slug names for the same dynamic path" error while providing clean URLs for institutional pages. Documented in .claude/decisions.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Bumps [next](https://github.com/vercel/next.js) from 16.0.1 to 16.0.3. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.0.1...v16.0.3) --- updated-dependencies: - dependency-name: next dependency-version: 16.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps next from 16.0.1 to 16.0.3.
Release notes
Sourced from next's releases.
... (truncated)
Commits
2eda33cv16.0.300cb5d9perf: revert to use the light safe stringify for is-error (#86053)de6bc15docs: keywords in system reqs and add browserslist (#85838)a51b804docs: cacheHandlers (#85311)a63951fTurbopack: remove unused function (#85974)8c29c11Update authentication.mdx: FixAuth0Link (#85953)25716c8Deployment adapter: fix metadata for "/" route (#85820)bf9c900Upgrade React fromfa50caf5-20251107to52684925-20251110(#85980)4212a86switch to slice in createRuntimePrefetchTransformStream (#85822)07a8657Fix Turbopack local fontfont-familydeclaration (#85913)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)