2025-03-03までの原文変更点を反映し、１２の翻訳完了。

Author: HiroKws

original-en/artisan.md

@@ -692,8 +692,7 @@ $this->newLine(3);
 <a name="tables"></a>
 #### Tables
 
-The `table` method makes it easy to correctly format multiple rows / columns of data. All you need to do is provide the column names and the data for the table and Laravel will
-automatically calculate the appropriate width and height of the table for you:
+The `table` method makes it easy to correctly format multiple rows / columns of data. All you need to do is provide the column names and the data for the table and Laravel will automatically calculate the appropriate width and height of the table for you:
 
 ```php
 use App\Models\User;

original-en/configuration.md

@@ -322,13 +322,11 @@ When accessing this hidden route, you will then be redirected to the `/` route o
 
 By default, Laravel determines if your application is in maintenance mode using a file-based system. This means to activate maintenance mode, the `php artisan down` command has to be executed on each server hosting your application.
 
-Alternatively, Laravel offers a cache-based method for handling maintenance mode. This method requires running the `php artisan down` command on just one server. To use this approach, modify the "driver" setting in the `config/app.php` file of your application to `cache`. Then, select a cache `store` that is accessible by all your servers. This ensures the maintenance mode status is consistently maintained across every server:
+Alternatively, Laravel offers a cache-based method for handling maintenance mode. This method requires running the `php artisan down` command on just one server. To use this approach, modify the maintenance mode variables in your application's `.env` file. You should select a cache `store` that is accessible by all of your servers. This ensures the maintenance mode status is consistently maintained across every server:
 
-```php
-'maintenance' => [
-    'driver' => 'cache',
-    'store' => 'database',
-],
+```ini
+APP_MAINTENANCE_DRIVER=cache
+APP_MAINTENANCE_STORE=database
 ```
 
 <a name="pre-rendering-the-maintenance-mode-view"></a>

original-en/container.md

@@ -349,6 +349,8 @@ You can create your own contextual attributes by implementing the `Illuminate\Co
 
 namespace App\Attributes;
 
+use Attribute;
+use Illuminate\Contracts\Container\Container;
 use Illuminate\Contracts\Container\ContextualAttribute;
 
 #[Attribute(Attribute::TARGET_PARAMETER)]

original-en/contributions.md

@@ -82,9 +82,9 @@ Informal discussion regarding bugs, new features, and implementation of existing
 <a name="which-branch"></a>
 ## Which Branch?
 
-**All** bug fixes should be sent to the latest version that supports bug fixes (currently `11.x`). Bug fixes should **never** be sent to the `master` branch unless they fix features that exist only in the upcoming release.
+**All** bug fixes should be sent to the latest version that supports bug fixes (currently `12.x`). Bug fixes should **never** be sent to the `master` branch unless they fix features that exist only in the upcoming release.
 
-**Minor** features that are **fully backward compatible** with the current release may be sent to the latest stable branch (currently `11.x`).
+**Minor** features that are **fully backward compatible** with the current release may be sent to the latest stable branch (currently `12.x`).
 
 **Major** new features or features with breaking changes should always be sent to the `master` branch, which contains the upcoming release.
 

original-en/errors.md

@@ -32,7 +32,7 @@ During local development, you should set the `APP_DEBUG` environment variable to
 <a name="reporting-exceptions"></a>
 ### Reporting Exceptions
 
-In Laravel, exception reporting is used to log exceptions or send them to an external service [Sentry](https://github.com/getsentry/sentry-laravel) or [Flare](https://flareapp.io). By default, exceptions will be logged based on your [logging](/docs/{{version}}/logging) configuration. However, you are free to log exceptions however you wish.
+In Laravel, exception reporting is used to log exceptions or send them to an external service like [Sentry](https://github.com/getsentry/sentry-laravel) or [Flare](https://flareapp.io). By default, exceptions will be logged based on your [logging](/docs/{{version}}/logging) configuration. However, you are free to log exceptions however you wish.
 
 If you need to report different types of exceptions in different ways, you may use the `report` exception method in your application's `bootstrap/app.php` to register a closure that should be executed when an exception of a given type needs to be reported. Laravel will determine what type of exception the closure reports by examining the type-hint of the closure:
 

original-en/helpers.md

@@ -66,6 +66,8 @@ Laravel includes a variety of global "helper" PHP functions. Many of these funct
 [Arr::pull](#method-array-pull)
 [Arr::query](#method-array-query)
 [Arr::random](#method-array-random)
+[Arr::reject](#method-array-reject)
+[Arr::select](#method-array-select)
 [Arr::set](#method-array-set)
 [Arr::shuffle](#method-array-shuffle)
 [Arr::sort](#method-array-sort)
@@ -828,6 +830,42 @@ $items = Arr::random($array, 2);
 // [2, 5] - (retrieved randomly)
 ```
 
+<a name="method-array-reject"></a>
+#### `Arr::reject()` {.collection-method}
+
+The `Arr::reject` method removes items from an array using the given closure:
+
+```php
+use Illuminate\Support\Arr;
+
+$array = [100, '200', 300, '400', 500];
+
+$filtered = Arr::reject($array, function (string|int $value, int $key) {
+    return is_string($value);
+});
+
+// [0 => 100, 2 => 300, 4 => 500]
+```
+
+<a name="method-array-select"></a>
+#### `Arr::select()` {.collection-method}
+
+The `Arr::select` method selects an array of values from an array:
+
+```php
+use Illuminate\Support\Arr;
+
+$array = [
+    ['id' => 1, 'name' => 'Desk', 'price' => 200],
+    ['id' => 2, 'name' => 'Table', 'price' => 150],
+    ['id' => 3, 'name' => 'Chair', 'price' => 300],
+];
+
+Arr::select($array, ['name', 'price']);
+
+// [['name' => 'Desk', 'price' => 200], ['name' => 'Table', 'price' => 150], ['name' => 'Chair', 'price' => 300]]
+```
+
 <a name="method-array-set"></a>
 #### `Arr::set()` {.collection-method}
 

original-en/http-tests.md

@@ -989,6 +989,7 @@ Laravel's `Illuminate\Testing\TestResponse` class provides a variety of custom a
 [assertMovedPermanently](#assert-moved-permanently)
 [assertContent](#assert-content)
 [assertNoContent](#assert-no-content)
+[assertStreamed](#assert-streamed)
 [assertStreamedContent](#assert-streamed-content)
 [assertNotFound](#assert-not-found)
 [assertOk](#assert-ok)
@@ -1004,7 +1005,7 @@ Laravel's `Illuminate\Testing\TestResponse` class provides a variety of custom a
 [assertSeeText](#assert-see-text)
 [assertSeeTextInOrder](#assert-see-text-in-order)
 [assertServerError](#assert-server-error)
-[assertServiceUnavailable](#assert-server-unavailable)
+[assertServiceUnavailable](#assert-service-unavailable)
 [assertSessionHas](#assert-session-has)
 [assertSessionHasInput](#assert-session-has-input)
 [assertSessionHasAll](#assert-session-has-all)
@@ -1472,6 +1473,13 @@ Assert that the response has the given HTTP status code and no content:
 $response->assertNoContent($status = 204);
 ```
 
+<a name="assert-streamed"></a>
+#### assertStreamed
+
+Assert that the response was a streamed response:
+
+    $response->assertStreamed();
+
 <a name="assert-streamed-content"></a>
 #### assertStreamedContent
 
@@ -1607,7 +1615,7 @@ Assert that the response has a server error (>= 500 , < 600) HTTP status code:
 $response->assertServerError();
 ```
 
-<a name="assert-server-unavailable"></a>
+<a name="assert-service-unavailable"></a>
 #### assertServiceUnavailable
 
 Assert that the response has a "Service Unavailable" (503) HTTP status code:
@@ -1822,6 +1830,12 @@ $response->assertInvalid([
 ]);
 ```
 
+If you would like to assert that the given fields are the only fields with validation errors, you may use the `assertOnlyInvalid` method:
+
+```php
+$response->assertOnlyInvalid(['name', 'email']);
+```
+
 <a name="assert-view-has"></a>
 #### assertViewHas
 

original-en/installation.md

@@ -9,14 +9,9 @@
     - [Environment Based Configuration](#environment-based-configuration)
     - [Databases and Migrations](#databases-and-migrations)
     - [Directory Configuration](#directory-configuration)
-- [Local Installation Using Herd](#local-installation-using-herd)
+- [Installation Using Herd](#installation-using-herd)
     - [Herd on macOS](#herd-on-macos)
     - [Herd on Windows](#herd-on-windows)
-- [Docker Installation Using Sail](#docker-installation-using-sail)
-    - [Sail on macOS](#sail-on-macos)
-    - [Sail on Windows](#sail-on-windows)
-    - [Sail on Linux](#sail-on-linux)
-    - [Choosing Your Sail Services](#choosing-your-sail-services)
 - [IDE Support](#ide-support)
 - [Next Steps](#next-steps)
     - [Laravel the Full Stack Framework](#laravel-the-fullstack-framework)
@@ -84,7 +79,7 @@ composer global require laravel/installer
 ```
 
 > [!NOTE]
-> For a fully-featured, graphical PHP installation and management experience, check out [Laravel Herd](#local-installation-using-herd).
+> For a fully-featured, graphical PHP installation and management experience, check out [Laravel Herd](#installation-using-herd).
 
 <a name="creating-an-application"></a>
 ### Creating an Application
@@ -150,15 +145,15 @@ php artisan migrate
 ```
 
 > [!NOTE]
-> If you are developing on macOS or Windows and need to install MySQL, PostgreSQL, or Redis locally, consider using [Herd Pro](https://herd.laravel.com/#plans).
+> If you are developing on macOS or Windows and need to install MySQL, PostgreSQL, or Redis locally, consider using [Herd Pro](https://herd.laravel.com/#plans) or [DBngin](https://dbngin.com/).
 
 <a name="directory-configuration"></a>
 ### Directory Configuration
 
 Laravel should always be served out of the root of the "web directory" configured for your web server. You should not attempt to serve a Laravel application out of a subdirectory of the "web directory". Attempting to do so could expose sensitive files present within your application.
 
-<a name="local-installation-using-herd"></a>
-## Local Installation Using Herd
+<a name="installation-using-herd"></a>
+## Installation Using Herd
 
 [Laravel Herd](https://herd.laravel.com) is a blazing fast, native Laravel and PHP development environment for macOS and Windows. Herd includes everything you need to get started with Laravel development, including PHP and Nginx.
 
@@ -207,150 +202,6 @@ herd open
 
 You can learn more about Herd by checking out the [Herd documentation for Windows](https://herd.laravel.com/docs/windows).
 
-<a name="docker-installation-using-sail"></a>
-## Docker Installation Using Sail
-
-We want it to be as easy as possible to get started with Laravel regardless of your preferred operating system. So, there are a variety of options for developing and running a Laravel application on your local machine. While you may wish to explore these options at a later time, Laravel provides [Sail](/docs/{{version}}/sail), a built-in solution for running your Laravel application using [Docker](https://www.docker.com).
-
-Docker is a tool for running applications and services in small, light-weight "containers" which do not interfere with your local machine's installed software or configuration. This means you don't have to worry about configuring or setting up complicated development tools such as web servers and databases on your local machine. To get started, you only need to install [Docker Desktop](https://www.docker.com/products/docker-desktop).
-
-Laravel Sail is a light-weight command-line interface for interacting with Laravel's default Docker configuration. Sail provides a great starting point for building a Laravel application using PHP, MySQL, and Redis without requiring prior Docker experience.
-
-> [!NOTE]
-> Already a Docker expert? Don't worry! Everything about Sail can be customized using the `docker-compose.yml` file included with Laravel.
-
-<a name="sail-on-macos"></a>
-### Sail on macOS
-
-If you're developing on a Mac and [Docker Desktop](https://www.docker.com/products/docker-desktop) is already installed, you can use a simple terminal command to create a new Laravel application. For example, to create a new Laravel application in a directory named "example-app", you may run the following command in your terminal:
-
-```shell
-curl -s "https://laravel.build/example-app" | bash
-```
-
-Of course, you can change "example-app" in this URL to anything you like - just make sure the application name only contains alpha-numeric characters, dashes, and underscores. The Laravel application's directory will be created within the directory you execute the command from.
-
-Sail installation may take several minutes while Sail's application containers are built on your local machine.
-
-After the application has been created, you can navigate to the application directory and start Laravel Sail. Laravel Sail provides a simple command-line interface for interacting with Laravel's default Docker configuration:
-
-```shell
-cd example-app
-
-./vendor/bin/sail up
-```
-
-Once the application's Docker containers have started, you should run your application's [database migrations](/docs/{{version}}/migrations):
-
-```shell
-./vendor/bin/sail artisan migrate
-```
-
-Finally, you can access the application in your web browser at: http://localhost.
-
-> [!NOTE]
-> To continue learning more about Laravel Sail, review its [complete documentation](/docs/{{version}}/sail).
-
-<a name="sail-on-windows"></a>
-### Sail on Windows
-
-Before we create a new Laravel application on your Windows machine, make sure to install [Docker Desktop](https://www.docker.com/products/docker-desktop). Next, you should ensure that Windows Subsystem for Linux 2 (WSL2) is installed and enabled. WSL allows you to run Linux binary executables natively on Windows 10. Information on how to install and enable WSL2 can be found within Microsoft's [developer environment documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10).
-
-> [!NOTE]
-> After installing and enabling WSL2, you should ensure that Docker Desktop is [configured to use the WSL2 backend](https://docs.docker.com/docker-for-windows/wsl/).
-
-Next, you are ready to create your first Laravel application. Launch [Windows Terminal](https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701?rtc=1&activetab=pivot:overviewtab) and begin a new terminal session for your WSL2 Linux operating system. Next, you can use a simple terminal command to create a new Laravel application. For example, to create a new Laravel application in a directory named "example-app", you may run the following command in your terminal:
-
-```shell
-curl -s https://laravel.build/example-app | bash
-```
-
-Of course, you can change "example-app" in this URL to anything you like - just make sure the application name only contains alpha-numeric characters, dashes, and underscores. The Laravel application's directory will be created within the directory you execute the command from.
-
-Sail installation may take several minutes while Sail's application containers are built on your local machine.
-
-After the application has been created, you can navigate to the application directory and start Laravel Sail. Laravel Sail provides a simple command-line interface for interacting with Laravel's default Docker configuration:
-
-```shell
-cd example-app
-
-./vendor/bin/sail up
-```
-
-Once the application's Docker containers have started, you should run your application's [database migrations](/docs/{{version}}/migrations):
-
-```shell
-./vendor/bin/sail artisan migrate
-```
-
-Finally, you can access the application in your web browser at: http://localhost.
-
-> [!NOTE]
-> To continue learning more about Laravel Sail, review its [complete documentation](/docs/{{version}}/sail).
-
-#### Developing Within WSL2
-
-Of course, you will need to be able to modify the Laravel application files that were created within your WSL2 installation. To accomplish this, we recommend using Microsoft's [Visual Studio Code](https://code.visualstudio.com) editor and their first-party extension for [Remote Development](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack).
-
-Once these tools are installed, you may open any Laravel application by executing the `code .` command from your application's root directory using Windows Terminal.
-
-<a name="sail-on-linux"></a>
-### Sail on Linux
-
-If you're developing on Linux and [Docker Compose](https://docs.docker.com/compose/install/) is already installed, you can use a simple terminal command to create a new Laravel application.
-
-First, if you are using Docker Desktop for Linux, you should execute the following command. If you are not using Docker Desktop for Linux, you may skip this step:
-
-```shell
-docker context use default
-```
-
-Then, to create a new Laravel application in a directory named "example-app", you may run the following command in your terminal:
-
-```shell
-curl -s https://laravel.build/example-app | bash
-```
-
-Of course, you can change "example-app" in this URL to anything you like - just make sure the application name only contains alpha-numeric characters, dashes, and underscores. The Laravel application's directory will be created within the directory you execute the command from.
-
-Sail installation may take several minutes while Sail's application containers are built on your local machine.
-
-After the application has been created, you can navigate to the application directory and start Laravel Sail. Laravel Sail provides a simple command-line interface for interacting with Laravel's default Docker configuration:
-
-```shell
-cd example-app
-
-./vendor/bin/sail up
-```
-
-Once the application's Docker containers have started, you should run your application's [database migrations](/docs/{{version}}/migrations):
-
-```shell
-./vendor/bin/sail artisan migrate
-```
-
-Finally, you can access the application in your web browser at: http://localhost.
-
-> [!NOTE]
-> To continue learning more about Laravel Sail, review its [complete documentation](/docs/{{version}}/sail).
-
-<a name="choosing-your-sail-services"></a>
-### Choosing Your Sail Services
-
-When creating a new Laravel application via Sail, you may use the `with` query string variable to choose which services should be configured in your new application's `docker-compose.yml` file. Available services include `mysql`, `pgsql`, `mariadb`, `redis`, `valkey`, `memcached`, `meilisearch`, `typesense`, `minio`, `selenium`, and `mailpit`:
-
-```shell
-curl -s "https://laravel.build/example-app?with=mysql,redis" | bash
-```
-
-If you do not specify which services you would like configured, a default stack of `mysql`, `redis`, `meilisearch`, `mailpit`, and `selenium` will be configured.
-
-You may instruct Sail to install a default [Devcontainer](/docs/{{version}}/sail#using-devcontainers) by adding the `devcontainer` parameter to the URL:
-
-```shell
-curl -s "https://laravel.build/example-app?with=mysql,redis&devcontainer" | bash
-```
-
 <a name="ide-support"></a>
 ## IDE Support