[tl! add]
```
-Next, you may navigate to your application's `/login` or `/register` URLs in your web browser. All of Breeze's routes are defined within the `routes/auth.php` file.
+
+#### Authentication Page Layout Variants
-
-### Breeze and Next.js / API
+The authentication pages included with the Vue starter kit, such as the login page and registration page, also offer three different layout variants: "simple", "card", and "split".
-Laravel Breeze can also scaffold an authentication API that is ready to authenticate modern JavaScript applications such as those powered by [Next](https://nextjs.org), [Nuxt](https://nuxt.com), and others. To get started, select the API stack as your desired stack when executing the `breeze:install` Artisan command:
+To change your authentication layout, modify the layout that is imported at the top of your application's `resources/js/layouts/AuthLayout.vue` file:
-```shell
-php artisan breeze:install
+```js
+import AuthLayout from '@/layouts/auth/AuthSimpleLayout.vue'; // [tl! remove]
+import AuthLayout from '@/layouts/auth/AuthSplitLayout.vue'; // [tl! add]
+```
-php artisan migrate
+
+### Livewire
+
+Our Livewire starter kit is built with Livewire 3, Laravel Volt, Tailwind, and [Flux UI](https://fluxui.dev/). As with all of our starter kits, all of the backend and frontend code exists within your application to allow for full customization.
+
+The majority of the frontend code is located in the `resources/views` directory. You are free to modify any of the code to customize the appearance and behavior of your application:
+
+```text
+resources/views
+├── components # Reusable Livewire components
+├── flux # Customized Flux components
+├── livewire # Livewire pages
+├── partials # Reusable Blade partials
+├── dashboard.blade.php # Authenticated user dashboard
+├── welcome.blade.php # Guest user welcome page
```
-During installation, Breeze will add a `FRONTEND_URL` environment variable to your application's `.env` file. This URL should be the URL of your JavaScript application. This will typically be `http://localhost:3000` during local development. In addition, you should ensure that your `APP_URL` is set to `http://localhost:8000`, which is the default URL used by the `serve` Artisan command.
+
+#### Available Layouts
+
+The Livewire starter kit includes two different primary layouts for you choose from: a "sidebar" layout and a "header" layout. The sidebar layout is the default, but you can switch to the header layout by modifying the layout that is used by your application's `resources/views/components/layouts/app.blade.php` file. In addition, you should add the `container` attribute to the main Flux component:
+
+```blade
+
+
+ {{ $slot }}
+
+
+```
+
+
+#### Authentication Page Layout Variants
+
+The authentication pages included with the Livewire starter kit, such as the login page and registration page, also offer three different layout variants: "simple", "card", and "split".
+
+To change your authentication layout, modify the layout that is used by your application's `resources/views/components/layouts/auth.blade.php` file:
+
+```blade
+
+ {{ $slot }}
+
+```
-
-#### Next.js Reference Implementation
+
+## WorkOS AuthKit Authentication
+
+By default, the React, Vue, and Livewire starter kits all utilize Laravel's built-in authentication system to offer login, registration, password reset, email verification, and more. In addition, we also offer a [WorkOS AuthKit](https://authkit.com) powered variant of each starter kit that offers:
+
+
+
+- Social authentication (Google, Microsoft, GitHub, and Apple)
+- Passkey authentication
+- Email based "Magic Auth"
+- SSO
+
+
+
+Using WorkOS as your authentication provider [requires a WorkOS account](https://workos.com). WorkOS offers free authentication for applications up to 1 million monthly active users.
+
+To use WorkOS AuthKit as your application's authentication provider, select the WorkOS option when creating your new starter kit powered application via `laravel new`.
+
+### Configuring Your WorkOS Starter Kit
+
+After creating a new application using a WorkOS powered starter kit, you should set the `WORKOS_CLIENT_ID`, `WORKOS_API_KEY`, and `WORKOS_REDIRECT_URL` environment variables in your application's `.env` file. These variables should match the values provided to you in the WorkOS dashboard for your application:
+
+```ini
+WORKOS_CLIENT_ID=your-client-id
+WORKOS_API_KEY=your-api-key
+WORKOS_REDIRECT_URL="${APP_URL}/authenticate"
+```
-Finally, you are ready to pair this backend with the frontend of your choice. A Next reference implementation of the Breeze frontend is [available on GitHub](https://github.com/laravel/breeze-next). This frontend is maintained by Laravel and contains the same user interface as the traditional Blade and Inertia stacks provided by Breeze.
+
+#### Configuring AuthKit Authentication Methods
-
-## Laravel Jetstream
+When using a WorkOS powered starter kit, we recommend that you disable "Email + Password" authentication within your application's WorkOS AuthKit configuration settings, allowing users to only authenticate via social authentication providers, passkeys, "Magic Auth", and SSO. This allows your application to totally avoid handling user passwords.
-While Laravel Breeze provides a simple and minimal starting point for building a Laravel application, Jetstream augments that functionality with more robust features and additional frontend technology stacks. **For those brand new to Laravel, we recommend learning the ropes with Laravel Breeze before graduating to Laravel Jetstream.**
+
+#### Configuring AuthKit Session Timeouts
+
+In addition, we recommend that you configure your WorkOS AuthKit session inactivity timeout to match your Laravel application's configured session timeout threshold, which is typically two hours.
+
+
+### Frequently Asked Questions
+
+
+#### How do I upgrade?
+
+Every starter kit gives you a solid starting point for your next application. With full ownership of the code, you can tweak, customize, and build your application exactly as you envision. However, there is no need to update the starter kit itself.
+
+
+#### How do I enable email verification?
+
+Email verification can be added by by uncommenting the `MustVerifyEmail` import in your `App/Models/User.php` model and ensuring the model implements the `MustVerifyEmail` interface:
+
+```php
+group(function () {
+ Route::get('dashboard', function () {
+ return Inertia::render('dashboard');
+ })->name('dashboard');
+});
+```
+
+> [!NOTE]
+> Email verification is not required when using the [WorkOS](#workos) variant of the starter kits.
+
+
+#### How do I modify the default email template?
+
+You may want to customize the default email template to better align with your application's branding. To modify this template, you should publish the email views to your application with the following command:
+
+```
+php artisan vendor:publish --tag=laravel-mail
+```
-Jetstream provides a beautifully designed application scaffolding for Laravel and includes login, registration, email verification, two-factor authentication, session management, API support via Laravel Sanctum, and optional team management. Jetstream is designed using [Tailwind CSS](https://tailwindcss.com) and offers your choice of [Livewire](https://livewire.laravel.com) or [Inertia](https://inertiajs.com) driven frontend scaffolding.
+This will generate several files in `resources/views/vendor/mail`. You can modify any of these files as well as the `resources/views/vendor/mail/themes/default.css` file to change the look and appearance of the default email template.
-Complete documentation for installing Laravel Jetstream can be found within the [official Jetstream documentation](https://jetstream.laravel.com).
diff --git a/structure.md b/structure.md
index 669241f1fd..e1b62d043f 100644
--- a/structure.md
+++ b/structure.md
@@ -32,9 +32,6 @@
The default Laravel application structure is intended to provide a great starting point for both large and small applications. But you are free to organize your application however you like. Laravel imposes almost no restrictions on where any given class is located - as long as Composer can autoload the class.
-> [!NOTE]
-> New to Laravel? Check out the [Laravel Bootcamp](https://bootcamp.laravel.com) for a hands-on tour of the framework while we walk you through building your first Laravel application.
-
## The Root Directory
diff --git a/upgrade.md b/upgrade.md
index 9c5d64fa7c..90192fa701 100644
--- a/upgrade.md
+++ b/upgrade.md
@@ -7,16 +7,7 @@
-- TBD
-
-
-
-
-## Medium Impact Changes
-
-
-
-- TBD
+- [Updating Dependencies](#updating-dependencies)
@@ -25,15 +16,17 @@
-- TBD
+- [Carbon 3](#carbon-3)
+- [Concurrency Result Index Mapping](#concurrency-result-index-mapping)
+- [Image Validation Now Excludes SVGs](#image-validation)
+- [Nested Array Request Merging](#nested-array-request-merging)
## Upgrading To 12.0 From 11.x
-
-#### Estimated Upgrade Time: ?? Minutes
+#### Estimated Upgrade Time: 5 Minutes
> [!NOTE]
> We attempt to document every possible breaking change. Since some of these breaking changes are in obscure parts of the framework only a portion of these changes may actually affect your application. Want to save time? You can use [Laravel Shift](https://laravelshift.com/) to help automate your application upgrades.
@@ -51,7 +44,66 @@ You should update the following dependencies in your application's `composer.jso
+
+#### Carbon 3
+
+**Likelihood Of Impact: Low**
+
+Support for [Carbon 2.x](https://carbon.nesbot.com/docs/) has been removed. All Laravel 12 applications now require Carbon 3.x.
+
+
+### Concurrency
+
+
+#### Concurrency Result Index Mapping
+
+**Likelihood Of Impact: Low**
+
+When invoking the `Concurrency::run` method with an associative array, the results of the concurrent operations are now returned with their associated keys:
+
+```php
+$result = Concurrency::run([
+ 'task-1' => fn () => 1 + 1,
+ 'task-2' => fn () => 2 + 2,
+]);
+
+// ['task-1' => 2, 'task-2' => 4]
+```
+
+
+### Requests
+
+
+#### Nested Array Request Merging
+
+**Likelihood Of Impact: Low**
+
+The `$request->mergeIfMissing()` method now allows merging nested array data using "dot" notation. If you were previously relying on this method to create a top-level array key containing the "dot" notation version of the key, you may need to adjust your application to account for this new behavior:
+
+```php
+$request->mergeIfMissing([
+ 'user.last_name' => 'Otwell',
+]);
+```
+
+
+### Validation
+
+
+#### Image Validation Now Excludes SVGs
+
+The `image` validation rule no longer allows SVG images by default. If you would like to allow SVGs when using the `image` rule, you must explicitly allow them:
+
+```php
+use Illuminate\Validation\Rules\File;
+
+'photo' => 'required|image:allow_svg'
+
+// Or...
+'photo' => ['required', File::image(allowSvg: true)],
+```
+
### Miscellaneous
-We also encourage you to view the changes in the `laravel/laravel` [GitHub repository](https://github.com/laravel/laravel). While many of these changes are not required, you may wish to keep these files in sync with your application. Some of these changes will be covered in this upgrade guide, but others, such as changes to configuration files or comments, will not be. You can easily view the changes with the [GitHub comparison tool](https://github.com/laravel/laravel/compare/11.x...master) and choose which updates are important to you.
+We also encourage you to view the changes in the `laravel/laravel` [GitHub repository](https://github.com/laravel/laravel). While many of these changes are not required, you may wish to keep these files in sync with your application. Some of these changes will be covered in this upgrade guide, but others, such as changes to configuration files or comments, will not be. You can easily view the changes with the [GitHub comparison tool](https://github.com/laravel/laravel/compare/11.x...12.x) and choose which updates are important to you.
diff --git a/views.md b/views.md
index cc55a97243..6c03fa37bb 100644
--- a/views.md
+++ b/views.md
@@ -45,7 +45,7 @@ Route::get('/', function () {
Instead of writing their frontend templates in PHP via Blade, many developers have begun to prefer to write their templates using React or Vue. Laravel makes this painless thanks to [Inertia](https://inertiajs.com/), a library that makes it a cinch to tie your React / Vue frontend to your Laravel backend without the typical complexities of building an SPA.
-Our Breeze and Jetstream [starter kits](/docs/{{version}}/starter-kits) give you a great starting point for your next Laravel application powered by Inertia. In addition, the [Laravel Bootcamp](https://bootcamp.laravel.com) provides a full demonstration of building a Laravel application powered by Inertia, including examples in Vue and React.
+Our [React and Vue application starter kits](/docs/{{version}}/starter-kits) give you a great starting point for your next Laravel application powered by Inertia.
## Creating and Rendering Views
diff --git a/vite.md b/vite.md
index 7bdd9b9e10..7ab83151fd 100644
--- a/vite.md
+++ b/vite.md
@@ -347,7 +347,7 @@ export default defineConfig({
```
> [!NOTE]
-> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Vue, and Vite configuration. Check out [Laravel Breeze](/docs/{{version}}/starter-kits#breeze-and-inertia) for the fastest way to get started with Laravel, Vue, and Vite.
+> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Vue, and Vite configuration.These starter kits offer the fastest way to get started with Laravel, Vue, and Vite.
### React
@@ -385,7 +385,7 @@ You will also need to include the additional `@viteReactRefresh` Blade directive
The `@viteReactRefresh` directive must be called before the `@vite` directive.
> [!NOTE]
-> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, React, and Vite configuration. Check out [Laravel Breeze](/docs/{{version}}/starter-kits#breeze-and-inertia) for the fastest way to get started with Laravel, React, and Vite.
+> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, React, and Vite configuration.These starter kits offer the fastest way to get started with Laravel, React, and Vite.
### Inertia
@@ -410,7 +410,7 @@ createInertiaApp({
If you are using Vite's code splitting feature with Inertia, we recommend configuring [asset prefetching](#asset-prefetching).
> [!NOTE]
-> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Inertia, and Vite configuration. Check out [Laravel Breeze](/docs/{{version}}/starter-kits#breeze-and-inertia) for the fastest way to get started with Laravel, Inertia, and Vite.
+> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Inertia, and Vite configuration.These starter kits offer the fastest way to get started with Laravel, Inertia, and Vite.
### URL Processing
@@ -761,7 +761,7 @@ php artisan inertia:start-ssr
```
> [!NOTE]
-> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Inertia SSR, and Vite configuration. Check out [Laravel Breeze](/docs/{{version}}/starter-kits#breeze-and-inertia) for the fastest way to get started with Laravel, Inertia SSR, and Vite.
+> Laravel's [starter kits](/docs/{{version}}/starter-kits) already include the proper Laravel, Inertia SSR, and Vite configuration.These starter kits offer the fastest way to get started with Laravel, Inertia SSR, and Vite.
## Script and Style Tag Attributes
+Our Livewire starter kit provides the perfect starting point for building Laravel applications with a [Laravel Livewire](https://livewire.laravel.com) frontend.
-#### Laravel Bootcamp
+Livewire is a powerful way of building dynamic, reactive, frontend UIs using just PHP. It's a great fit for teams that primarily use Blade templates and are looking for a simpler alternative to JavaScript-driven SPA frameworks like React and Vue.
-If you're new to Laravel, feel free to jump into the [Laravel Bootcamp](https://bootcamp.laravel.com). The Laravel Bootcamp will walk you through building your first Laravel application using Breeze. It's a great way to get a tour of everything that Laravel and Breeze have to offer.
+The Livewire starter kit utilizes Laravel Volt, Tailwind, and the [Flux UI](https://fluxui.dev) component library.
-
-### Installation
+
+## Starter Kit Customization
-First, you should [create a new Laravel application](/docs/{{version}}/installation). If you create your application using the [Laravel installer](/docs/{{version}}/installation#creating-a-laravel-project), you will be prompted to install Laravel Breeze during the installation process. Otherwise, you will need to follow the manual installation instructions below.
+
+### React
-If you have already created a new Laravel application without a starter kit, you may manually install Laravel Breeze using Composer:
+Our React starter kit is built with Inertia 2, React 19, Tailwind 4, and [shadcn/ui](https://ui.shadcn.com). As with all of our starter kits, all of the backend and frontend code exists within your application to allow for full customization.
+
+The majority of the frontend code is located in the `resources/js` directory. You are free to modify any of the code to customize the appearance and behavior of your application:
+
+```text
+resources/js/
+├── components/ # Reusable React components
+├── hooks/ # React hooks
+├── layouts/ # Application layouts
+├── lib/ # Utility functions and configuration
+├── pages/ # Page components
+└── types/ # TypeScript definitions
+```
+
+To publish additional shadcn components, first [find the component you want to publish](https://ui.shadcn.com). Then, publish the component using `npx`:
```shell
-composer require laravel/breeze --dev
+npx shadcn@latest add switch
```
-After Composer has installed the Laravel Breeze package, you should run the `breeze:install` Artisan command. This command publishes the authentication views, routes, controllers, and other resources to your application. Laravel Breeze publishes all of its code to your application so that you have full control and visibility over its features and implementation.
+In this example, the command will publish the Switch component to `resources/js/components/ui/switch.tsx`. Once the component has been published, you can use it in any of your pages:
-The `breeze:install` command will prompt you for your preferred frontend stack and testing framework:
+```jsx
+import { Switch } from "@/components/ui/switch"
-```shell
-php artisan breeze:install
+const MyPage = () => {
+ return (
+