merge

Author: r1tsuu

.github/actions/start-database/action.yml

@@ -3,7 +3,7 @@ description: Starts the required database for tests
 
 inputs:
   database:
-    description: 'Database type: mongodb, mongodb-atlas, cosmosdb, documentdb, firestore, postgres, postgres-custom-schema, postgres-uuid, postgres-read-replica, postgres-read-replicas, vercel-postgres-read-replica, sqlite, sqlite-uuid, supabase, d1'
+    description: 'Database type: mongodb, mongodb-atlas, cosmosdb, documentdb, firestore, postgres, postgres-custom-schema, postgres-uuid, postgres-uuidv7, postgres-read-replica, postgres-read-replicas, vercel-postgres-read-replica, sqlite, sqlite-uuid, sqlite-uuidv7, supabase, d1'
     required: true
 
 outputs:

.github/workflows/int.config.ts

@@ -10,10 +10,12 @@ createIntConfig({
     'postgres',
     'postgres-custom-schema',
     'postgres-uuid',
+    'postgres-uuidv7',
     'postgres-read-replica',
     'supabase',
     'sqlite',
     'sqlite-uuid',
+    'sqlite-uuidv7',
   ],
   shards: 3,
 })

CLAUDE.md

@@ -71,6 +71,20 @@ Payload is a monorepo structured around Next.js, containing the core CMS platfor
   - Invalid: `payload.logger.error('message', err)` - don't pass error as second argument
   - Use `err` not `error`, use `msg` not `message` in object form
 
+### React Component File Structure
+
+Each React component should have its own named folder:
+
+```
+ComponentName/
+├── index.tsx       # Component implementation
+└── index.scss      # Styles (if applicable)
+```
+
+- **Do:** Create a folder per component with `index.tsx` and `index.scss`
+- **Don't:** Place multiple `ComponentName.tsx` files in a single folder with one shared `.scss` file
+- Re-export from barrel files (`index.ts`) when grouping related components in a parent directory
+
 ### Running Dev Server
 
 - `pnpm run dev` - Start dev server with default config (`test/_community/config.ts`)

CONTRIBUTING.md

@@ -134,9 +134,11 @@ Set `PAYLOAD_DATABASE` in your `.env` file to choose the database adapter:
 - `postgres` - PostgreSQL with pgvector and PostGIS
 - `postgres-custom-schema` - PostgreSQL with custom schema
 - `postgres-uuid` - PostgreSQL with UUID primary keys
+- `postgres-uuidv7` - PostgreSQL with UUID V7 primary keys
 - `postgres-read-replica` - PostgreSQL with read replica
 - `sqlite` - SQLite
 - `sqlite-uuid` - SQLite with UUID primary keys
+- `sqlite-uuidv7` - SQLite with UUID V7 primary keys
 - `supabase` - Supabase (PostgreSQL)
 - `d1` - D1 (SQLite)
 

docs/admin/react-hooks.mdx

@@ -348,6 +348,17 @@ The `useForm` hook returns an object with the following properties:
         value: '',
       },
     ],
+    [
+      {
+        value: "**`getDataByPath`**",
+      },
+      {
+        value: 'Returns form field data for the given field path. Useful when dealing with arrays, blocks, or other form state.',
+      },
+      {
+        value: '',
+      },
+    ],
     [
       {
         value: "**`setModified`**",

docs/authentication/custom-strategies.mdx

@@ -10,6 +10,8 @@ keywords: authentication, config, configuration, overview, documentation, Conten
   This is an advanced feature, so only attempt this if you are an experienced
   developer. Otherwise, just let Payload's built-in authentication handle user
   auth for you.
+
+  **Development Note:** Changes to custom authentication strategies require a full server restart to take effect. Auth strategies are not hot-reloaded during development. Consider using tools like `nodemon` for auto-restart functionality.
 </Banner>
 
 ### Creating a strategy

docs/configuration/collections.mdx

@@ -12,7 +12,7 @@ Collections are also used to achieve [Authentication](../authentication/overview
 
 Collections are the primary way to structure recurring data in your application, such as users, products, pages, posts, and other types of content that you might want to manage. Each Collection can have its own unique [Access Control](../access-control/overview), [Hooks](../hooks/overview), [Admin Options](#admin-options), and more.
 
-To define a Collection Config, use the `collection` property in your [Payload Config](./overview):
+To define a Collection Config, use the `collections` property in your [Payload Config](./overview):
 
 ```ts
 import { buildConfig } from 'payload'

docs/custom-components/dashboard.mdx

@@ -176,8 +176,6 @@ If you don't define a `defaultLayout`, the collections widget will be automatica
 
 ### User Customization
 
-{/* TODO: maybe a good GIF here? */}
-
 Users can customize their dashboard by:
 
 1. Clicking the dashboard dropdown in the breadcrumb

docs/custom-components/root-components.mdx

@@ -45,7 +45,7 @@ The following options are available:
 | `header`          | An array of Custom Components to be injected above the Payload header. [More details](#header).                                                                          |
 | `logout.Button`   | The button displayed in the sidebar that logs the user out. [More details](#logoutbutton).                                                                               |
 | `Nav`             | Contains the sidebar / mobile menu in its entirety. [More details](#nav).                                                                                                |
-| `settingsMenu`    | An array of Custom Components to inject into a popup menu accessible via a gear icon above the logout button. [More details](#settingsMenu).                             |
+| `settingsMenu`    | An array of Custom Components to inject into a popup menu accessible via a gear icon above the logout button. [More details](#settingsmenu).                             |
 | `providers`       | Custom [React Context](https://react.dev/learn/scaling-up-with-reducer-and-context) providers that will wrap the entire Admin Panel. [More details](./custom-providers). |
 | `views`           | Override or create new views within the Admin Panel. [More details](./custom-views).                                                                                     |
 

docs/database/migrations.mdx

@@ -245,7 +245,7 @@ A common set of scripts in a `package.json`, set up to run migrations in CI, mig
 ```js
   "scripts": {
     // For running in dev mode
-    "dev": "next dev --turbo --no-server-fast-refresh",
+    "dev": "next dev",
 
     // To build your Next + Payload app for production
     "build": "next build",