2025-10-20までの原文変更点反映。

Author: HiroKws

original-en/billing.md

@@ -612,7 +612,7 @@ public function stripeName(): string|null
 }
 ```
 
-Similarly, you may override the `stripeEmail`, `stripePhone`, `stripeAddress`, and `stripePreferredLocales` methods. These methods will sync information to their corresponding customer parameters when [updating the Stripe customer object](https://stripe.com/docs/api/customers/update). If you wish to take total control over the customer information sync process, you may override the `syncStripeCustomerDetails` method.
+Similarly, you may override the `stripeEmail`, `stripePhone` (20 character maximum), `stripeAddress`, and `stripePreferredLocales` methods. These methods will sync information to their corresponding customer parameters when [updating the Stripe customer object](https://stripe.com/docs/api/customers/update). If you wish to take total control over the customer information sync process, you may override the `syncStripeCustomerDetails` method.
 
 <a name="billing-portal"></a>
 ### Billing Portal

original-en/blade.md

@@ -640,6 +640,20 @@ Since the `@once` directive is often used in conjunction with the `@push` or `@p
 @endPushOnce
 ```
 
+If you are pushing duplicate content from two separate Blade templates, you should provide a unique identifier as the second argument to the `@pushOnce` directive to ensure the content is only rendered once:
+
+```blade
+<!-- pie-chart.blade.php -->
+@pushOnce('scripts', 'chart.js')
+    <script src="/chart.js"></script>
+@endPushOnce
+
+<!-- line-chart.blade.php -->
+@pushOnce('scripts', 'chart.js')
+    <script src="/chart.js"></script>
+@endPushOnce
+```
+
 <a name="raw-php"></a>
 ### Raw PHP
 
@@ -720,14 +734,6 @@ php artisan make:component Forms/Input
 
 The command above will create an `Input` component in the `app/View/Components/Forms` directory and the view will be placed in the `resources/views/components/forms` directory.
 
-If you would like to create an anonymous component (a component with only a Blade template and no class), you may use the `--view` flag when invoking the `make:component` command:
-
-```shell
-php artisan make:component forms.input --view
-```
-
-The command above will create a Blade file at `resources/views/components/forms/input.blade.php` which can be rendered as a component via `<x-forms.input />`.
-
 <a name="manually-registering-package-components"></a>
 #### Manually Registering Package Components
 
@@ -1215,6 +1221,7 @@ By default, some keywords are reserved for Blade's internal use in order to rend
 
 - `data`
 - `render`
+- `resolve`
 - `resolveView`
 - `shouldRender`
 - `view`
@@ -1453,6 +1460,14 @@ You may use the `.` character to indicate if a component is nested deeper inside
 <x-inputs.button/>
 ```
 
+To create an anonymous component via Artisan, you may use the `--view` flag when invoking the `make:component` command:
+
+```shell
+php artisan make:component forms.input --view
+```
+
+The command above will create a Blade file at `resources/views/components/forms/input.blade.php` which can be rendered as a component via `<x-forms.input />`.
+
 <a name="anonymous-index-components"></a>
 ### Anonymous Index Components
 

original-en/controllers.md

@@ -129,7 +129,7 @@ namespace App\Http\Controllers;
 use Illuminate\Routing\Controllers\HasMiddleware;
 use Illuminate\Routing\Controllers\Middleware;
 
-class UserController extends Controller implements HasMiddleware
+class UserController implements HasMiddleware
 {
     /**
      * Get the middleware that should be assigned to the controller.

original-en/http-client.md

@@ -564,6 +564,7 @@ Another way of working with concurrent requests in Laravel is to use the `batch`
 
 ```php
 use Illuminate\Http\Client\Batch;
+use Illuminate\Http\Client\ConnectionException;
 use Illuminate\Http\Client\RequestException;
 use Illuminate\Http\Client\Response;
 use Illuminate\Support\Facades\Http;
@@ -578,7 +579,7 @@ $responses = Http::batch(fn (Batch $batch) => [
     // An individual request has completed successfully...
 })->then(function (Batch $batch, array $results) {
     // All requests completed successfully...
-})->catch(function (Batch $batch, int|string $key, Response|RequestException $response) {
+})->catch(function (Batch $batch, int|string $key, Response|RequestException|ConnectionException $response) {
     // First batch request failure detected...
 })->finally(function (Batch $batch, array $results) {
     // The batch has finished executing...
@@ -621,6 +622,23 @@ $batch->finished();
 // Indicates if the batch has request failures...
 $batch->hasFailures();
 ```
+<a name="deferring-batches"></a>
+#### Deferring Batches
+
+When the `defer` method is invoked, the batch of requests is not executed immediately. Instead, Laravel will execute the batch after the current application request's HTTP response has been sent to the user, keeping your application feeling fast and responsive:
+
+```php
+use Illuminate\Http\Client\Batch;
+use Illuminate\Support\Facades\Http;
+
+$responses = Http::batch(fn (Batch $batch) => [
+    $batch->get('http://localhost/first'),
+    $batch->get('http://localhost/second'),
+    $batch->get('http://localhost/third'),
+])->then(function (Batch $batch, array $results) {
+    // All requests completed successfully...
+})->defer();
+```
 
 <a name="macros"></a>
 ## Macros

original-en/mail.md

@@ -48,7 +48,7 @@ Within your `mail` configuration file, you will find a `mailers` configuration a
 <a name="driver-prerequisites"></a>
 ### Driver / Transport Prerequisites
 
-The API based drivers such as Mailgun, Postmark, Resend, and MailerSend are often simpler and faster than sending mail via SMTP servers. Whenever possible, we recommend that you use one of these drivers.
+The API based drivers such as Mailgun, Postmark, and Resend are often simpler and faster than sending mail via SMTP servers. Whenever possible, we recommend that you use one of these drivers.
 
 <a name="mailgun-driver"></a>
 #### Mailgun Driver
@@ -208,35 +208,6 @@ If you would like to define [additional options](https://docs.aws.amazon.com/aws
 ],
 ```
 
-<a name="mailersend-driver"></a>
-#### MailerSend Driver
-
-[MailerSend](https://www.mailersend.com/), a transactional email and SMS service, maintains their own API based mail driver for Laravel. The package containing the driver may be installed via the Composer package manager:
-
-```shell
-composer require mailersend/laravel-driver
-```
-
-Once the package is installed, add the `MAILERSEND_API_KEY` environment variable to your application's `.env` file. In addition, the `MAIL_MAILER` environment variable should be defined as `mailersend`:
-
-```ini
-MAIL_MAILER=mailersend
-MAIL_FROM_ADDRESS=app@yourdomain.com
-MAIL_FROM_NAME="App Name"
-
-MAILERSEND_API_KEY=your-api-key
-```
-
-Finally, add MailerSend to the `mailers` array in your application's `config/mail.php` configuration file:
-
-```php
-'mailersend' => [
-    'transport' => 'mailersend',
-],
-```
-
-To learn more about MailerSend, including how to use hosted templates, consult the [MailerSend driver documentation](https://github.com/mailersend/mailersend-laravel-driver#usage).
-
 <a name="failover-configuration"></a>
 ### Failover Configuration
 

original-en/queues.md

@@ -21,6 +21,7 @@
     - [Customizing The Queue and Connection](#customizing-the-queue-and-connection)
     - [Specifying Max Job Attempts / Timeout Values](#max-job-attempts-and-timeout)
     - [SQS FIFO and Fair Queues](#sqs-fifo-and-fair-queues)
+    - [Queue Failover](#queue-failover)
     - [Error Handling](#error-handling)
 - [Job Batching](#job-batching)
     - [Defining Batchable Jobs](#defining-batchable-jobs)
@@ -1531,6 +1532,31 @@ $invoicePaid = (new InvoicePaid($invoice))
 $user->notify($invoicePaid);
 ```
 
+<a name="queue-failover"></a>
+### Queue Failover
+
+The `failover` queue driver provides automatic failover functionality when pushing jobs to the queue. If the primary queue connection fails for any reason, Laravel will automatically attempt to push the job to the next configured connection in the list. This is particularly useful for ensuring high availability in production environments where queue reliability is critical.
+
+To configure a failover queue connection, specify the `failover` driver and provide an array of connection names to attempt in order. By default, Laravel includes an example failover configuration in your application's `config/queue.php` configuration file:
+
+```php
+'failover' => [
+    'driver' => 'failover',
+    'connections' => [
+        'database',
+        'sync',
+    ],
+],
+```
+
+Once you have configured a connection that uses the `failover` driver, you will probably want to set the failover connection as your default queue connection in your application's `.env` file:
+
+```ini
+QUEUE_CONNECTION=failover
+```
+
+When a queue connection operation fails and failover is activated, Laravel will dispatch the `Illuminate\Queue\Events\QueueFailedOver` event, allowing you to report or log that a queue connection has failed.
+
 <a name="error-handling"></a>
 ### Error Handling
 

original-en/scout.md

@@ -71,7 +71,7 @@ class Post extends Model
 <a name="queueing"></a>
 ### Queueing
 
-While not strictly required to use Scout, you should strongly consider configuring a [queue driver](/docs/{{version}}/queues) before using the library. Running a queue worker will allow Scout to queue all operations that sync your model information to your search indexes, providing much better response times for your application's web interface.
+When using an engine that is not the `database` or `collection` engine, you should strongly consider configuring a [queue driver](/docs/{{version}}/queues) before using the library. Running a queue worker will allow Scout to queue all operations that sync your model information to your search indexes, providing much better response times for your application's web interface.
 
 Once you have configured a queue driver, set the value of the `queue` option in your `config/scout.php` configuration file to `true`:
 
@@ -427,7 +427,7 @@ namespace App\Models;
 
 use Illuminate\Database\Eloquent\Model;
 use Laravel\Scout\Engines\Engine;
-use Laravel\Scout\EngineManager;
+use Laravel\Scout\Scout;
 use Laravel\Scout\Searchable;
 
 class User extends Model
@@ -439,7 +439,7 @@ class User extends Model
      */
     public function searchableUsing(): Engine
     {
-        return app(EngineManager::class)->engine('meilisearch');
+        return Scout::engine('meilisearch');
     }
 }
 ```
@@ -464,7 +464,7 @@ Enabling this feature will also pass the request's IP address and your authentic
 > [!WARNING]
 > The database engine currently supports MySQL and PostgreSQL.
 
-If your application interacts with small to medium sized databases or has a light workload, you may find it more convenient to get started with Scout's "database" engine. The database engine will use "where like" clauses and full text indexes when filtering results from your existing database to determine the applicable search results for your query.
+The `database` engine is the fastest way to get started with Laravel Scout, and uses MySQL / PostgreSQL full-text indexes and "where like" clauses when filtering results from your existing database to determine the applicable search results for your query.
 
 To use the database engine, you may simply set the value of the `SCOUT_DRIVER` environment variable to `database`, or specify the `database` driver directly in your application's `scout` configuration file:
 
@@ -522,7 +522,7 @@ Once you have specified the collection driver as your preferred driver, you may
 
 On first glance, the "database" and "collections" engines are fairly similar. They both interact directly with your database to retrieve search results. However, the collection engine does not utilize full text indexes or `LIKE` clauses to find matching records. Instead, it pulls all possible records and uses Laravel's `Str::is` helper to determine if the search string exists within the model attribute values.
 
-The collection engine is the most portable search engine as it works across all relational databases supported by Laravel (including SQLite and SQL Server); however, it is less efficient than Scout's database engine.
+The collection engine is the most portable search engine as it works across all relational databases supported by Laravel (including SQLite and SQL Server); however, it is much less efficient than Scout's database engine.
 
 <a name="indexing"></a>
 ## Indexing

translation-ja/billing.md

@@ -612,7 +612,7 @@ public function stripeName(): string|null
 }
 ```
 
-同様に、`stripeEmail`、`stripePhone`、`stripeAddress`、`stripePreferredLocales`メソッドをオーバーライドできます。これらのメソッドは、[Stripe顧客オブジェクトの更新](https://stripe.com/docs/api/customers/update)の際に、対応する顧客パラメータへ情報を同期します。顧客情報の同期プロセスを完全にコントロールしたい場合は、`syncStripeCustomerDetails`メソッドをオーバーライドできます。
+同様に、`stripeEmail`、`stripePhone`（最大20文字）、`stripeAddress`、`stripePreferredLocales`メソッドをオーバーライドできます。これらのメソッドは、[Stripe顧客オブジェクトの更新](https://stripe.com/docs/api/customers/update)の際に、対応する顧客パラメータへ情報を同期します。顧客情報の同期プロセスを完全にコントロールしたい場合は、`syncStripeCustomerDetails`メソッドをオーバーライドできます。
 
 <a name="billing-portal"></a>
 ### 請求ポータル

translation-ja/blade.md

@@ -640,6 +640,20 @@ Bladeの`@include`ディレクティブを使用すると、別のビュー内
 @endPushOnce
 ```
 
+２つの別々のBladeテンプレートから重複コンテンツをプッシュする場合、コンテンツが一度だけレンダされるように、`@pushOnce`ディレクティブの２番目の引数として一意の識別子を提供する必要があります。
+
+```blade
+<!-- pie-chart.blade.php -->
+@pushOnce('scripts', 'chart.js')
+    <script src="/chart.js"></script>
+@endPushOnce
+
+<!-- line-chart.blade.php -->
+@pushOnce('scripts', 'chart.js')
+    <script src="/chart.js"></script>
+@endPushOnce
+```
+
 <a name="raw-php"></a>
 ### 生PHP
 
@@ -720,14 +734,6 @@ php artisan make:component Forms/Input
 
 上記のコマンドは、`app/View/Components/Forms`ディレクトリに`Input`コンポーネントを作成し、ビューは`resources/views/components/forms`ディレクトリに配置します。
 
-匿名コンポーネント(Bladeテンプレートのみでクラスを持たないコンポーネント)を作成したい場合は、`make:component`コマンドを実行するとき、`--view`フラグを使用します。
-
-```shell
-php artisan make:component forms.input --view
-```
-
-上記のコマンドは、`resources/views/components/forms/input.blade.php`へBladeファイルを作成します。このファイルは`<x-forms.input />`により、コンポーネントとしてレンダできます。
-
 <a name="manually-registering-package-components"></a>
 #### パッケージコンポーネントの手作業登録
 
@@ -1215,6 +1221,7 @@ class Alert extends Component
 
 - `data`
 - `render`
+- `resolve`
 - `resolveView`
 - `shouldRender`
 - `view`
@@ -1453,6 +1460,14 @@ Bladeは、コンポーネント名のパスカルケースを使い、コンポ
 <x-inputs.button/>
 ```
 
+Artisanで匿名コンポーネントを作成するには、`make:component`コマンドを実行する際に`--view`フラグを使用します。
+
+```shell
+php artisan make:component forms.input --view
+```
+
+上記コマンドは、`resources/views/components/forms/input.blade.php`にBladeファイルを作成します。このファイルは `<x-forms.input />`を使い、コンポーネントとしてレンダできます。
+
 <a name="anonymous-index-components"></a>
 ### 匿名インデックスコンポーネント
 

translation-ja/controllers.md

@@ -129,7 +129,7 @@ namespace App\Http\Controllers;
 use Illuminate\Routing\Controllers\HasMiddleware;
 use Illuminate\Routing\Controllers\Middleware;
 
-class UserController extends Controller implements HasMiddleware
+class UserController implements HasMiddleware
 {
     /**
      * コントローラへ指定するミドルウェアを取得