2025年11月24日までの原文変更点反映。

Author: HiroKws

original-en/blade.md

@@ -1855,6 +1855,16 @@ If you would like to prepend content onto the beginning of a stack, you should u
 @endprepend
 ```
 
+The `@hasstack` directive may be used to determine if a stack is empty:
+
+```blade
+@hasstack('list')
+    <ul>
+        @stack('list')
+    </ul>
+@endif
+```
+
 <a name="service-injection"></a>
 ## Service Injection
 

original-en/mail.md

@@ -111,7 +111,7 @@ Next, set the `default` option in your application's `config/mail.php` configura
 
 ```php
 'postmark' => [
-    'key' => env('POSTMARK_API_TOKEN'),
+    'key' => env('POSTMARK_API_KEY'),
 ],
 ```
 

original-en/mcp.md

@@ -29,6 +29,7 @@
     - [Resource Dependency Injection](#resource-dependency-injection)
     - [Conditional Resource Registration](#conditional-resource-registration)
     - [Resource Responses](#resource-responses)
+- [Metadata](#metadata)
 - [Authentication](#authentication)
     - [OAuth 2.1](#oauth)
     - [Sanctum](#sanctum)
@@ -1116,6 +1117,63 @@ To indicate an error occurred during resource retrieval, use the `error()` metho
 return Response::error('Unable to fetch weather data for the specified location.');
 ```
 
+<a name="metadata"></a>
+## Metadata
+
+Laravel MCP also supports the `_meta` field as defined in the [MCP specification](https://modelcontextprotocol.io/specification/2025-06-18/basic#meta), which is required by certain MCP clients or integrations. Metadata can be applied to all MCP primitives, including tools, resources, and prompts, as well as their responses.
+
+You can attach metadata to individual response content using the `withMeta` method:
+
+```php
+use Laravel\Mcp\Request;
+use Laravel\Mcp\Response;
+
+/**
+ * Handle the tool request.
+ */
+public function handle(Request $request): Response
+{
+    return Response::text('The weather is sunny.')
+        ->withMeta(['source' => 'weather-api', 'cached' => true]);
+}
+```
+
+For result-level metadata that applies to the entire response envelope, wrap your responses with `Response::make` and call `withMeta` on the returned response factory instance:
+
+```php
+use Laravel\Mcp\Request;
+use Laravel\Mcp\Response;
+use Laravel\Mcp\ResponseFactory;
+
+/**
+ * Handle the tool request.
+ */
+public function handle(Request $request): ResponseFactory
+{
+    return Response::make(
+        Response::text('The weather is sunny.')
+    )->withMeta(['request_id' => '12345']);
+}
+```
+
+To attach metadata to a tool, resource, or prompt itself, define a `$meta` property on the class:
+
+```php
+use Laravel\Mcp\Server\Tool;
+
+class CurrentWeatherTool extends Tool
+{
+    protected string $description = 'Fetches the current weather forecast.';
+
+    protected ?array $meta = [
+        'version' => '2.0',
+        'author' => 'Weather Team',
+    ];
+
+    // ...
+}
+```
+
 <a name="authentication"></a>
 ## Authentication
 

original-en/precognition.md

@@ -16,7 +16,7 @@
 <a name="introduction"></a>
 ## Introduction
 
-Laravel Precognition allows you to anticipate the outcome of a future HTTP request. One of the primary use cases of Precognition is the ability to provide "live" validation for your frontend JavaScript application without having to duplicate your application's backend validation rules. Precognition pairs especially well with Laravel's Inertia-based [starter kits](/docs/{{version}}/starter-kits).
+Laravel Precognition allows you to anticipate the outcome of a future HTTP request. One of the primary use cases of Precognition is the ability to provide "live" validation for your frontend JavaScript application without having to duplicate your application's backend validation rules.
 
 When Laravel receives a "precognitive request", it will execute all of the route's middleware and resolve the route's controller dependencies, including validating [form requests](/docs/{{version}}/validation#form-request-validation) - but it will not actually execute the route's controller method.
 

original-en/queues.md

@@ -890,7 +890,7 @@ ProcessPodcast::dispatchIf($accountActive, $podcast);
 ProcessPodcast::dispatchUnless($accountSuspended, $podcast);
 ```
 
-In new Laravel applications, the `database` driver is the default queue driver. You may specify a different queue driver within your application's `config/queue.php` configuration file.
+In new Laravel applications, the `database` connection is defined as the default queue. You may specify a different default queue connection by changing the `QUEUE_CONNECTION` environment variable in your application's `.env` file.
 
 <a name="delayed-dispatching"></a>
 ### Delayed Dispatching

original-en/releases.md

@@ -24,11 +24,11 @@ For all Laravel releases, bug fixes are provided for 18 months and security fixe
 <div class="overflow-auto">
 
 | Version | PHP (*)   | Release             | Bug Fixes Until     | Security Fixes Until |
-| ------- | --------- | ------------------- | ------------------- | -------------------- |
+| ------- |-----------| ------------------- | ------------------- | -------------------- |
 | 10      | 8.1 - 8.3 | February 14th, 2023 | August 6th, 2024    | February 4th, 2025   |
 | 11      | 8.2 - 8.4 | March 12th, 2024    | September 3rd, 2025 | March 12th, 2026     |
-| 12      | 8.2 - 8.4 | February 24th, 2025 | August 13th, 2026   | February 24th, 2027  |
-| 13      | 8.3 - 8.4 | Q1 2026             | Q3 2027             | Q1 2028              |
+| 12      | 8.2 - 8.5 | February 24th, 2025 | August 13th, 2026   | February 24th, 2027  |
+| 13      | 8.3 - 8.5 | Q1 2026             | Q3 2027             | Q1 2028              |
 
 </div>
 

original-en/scheduling.md

@@ -168,6 +168,7 @@ We've already seen a few examples of how you may configure a task to run at spec
 | `->dailyAt('13:00');`              | Run the task every day at 13:00.                         |
 | `->twiceDaily(1, 13);`             | Run the task daily at 1:00 & 13:00.                      |
 | `->twiceDailyAt(1, 13, 15);`       | Run the task daily at 1:15 & 13:15.                      |
+| `->daysOfMonth([1, 10, 20]);`      | Run the task on specific days of the month.              |
 | `->weekly();`                      | Run the task every Sunday at 00:00.                      |
 | `->weeklyOn(1, '8:00');`           | Run the task every week on Monday at 8:00.               |
 | `->monthly();`                     | Run the task on the first day of every month at 00:00.   |

original-en/testing.md

@@ -7,7 +7,7 @@
     - [Running Tests in Parallel](#running-tests-in-parallel)
     - [Reporting Test Coverage](#reporting-test-coverage)
     - [Profiling Tests](#profiling-tests)
-- [Caching Configuration](#caching-configuration)
+- [Configuration Caching](#configuration-caching)
 
 <a name="introduction"></a>
 ## Introduction

original-en/validation.md

@@ -1075,6 +1075,7 @@ Below is a list of all available validation rules and their function:
 
 [Between](#rule-between)
 [Dimensions](#rule-dimensions)
+[Encoding](#rule-encoding)
 [Extensions](#rule-extensions)
 [File](#rule-file)
 [Image](#rule-image)
@@ -1575,6 +1576,24 @@ $request->validate([
 > [!WARNING]
 > The `dns` and `spoof` validators require the PHP `intl` extension.
 
+<a name="rule-encoding"></a>
+#### encoding:*encoding_type*
+
+The field under validation must match the specified character encoding. This rule uses PHP's `mb_check_encoding` function to verify the encoding of the given file or string value. For convenience, the `encoding` rule may be constructed using Laravel's fluent file rule builder:
+
+```php
+use Illuminate\Support\Facades\Validator;
+use Illuminate\Validation\Rules\File;
+
+Validator::validate($input, [
+    'attachment' => [
+        'required',
+        File::types(['csv'])
+            ->encoding('utf-8'),
+    ],
+]);
+```
+
 <a name="rule-ends-with"></a>
 #### ends_with:_foo_,_bar_,...
 

translation-ja/blade.md

@@ -1855,6 +1855,16 @@ Bladeを使用すると、別のビューまたはレイアウトのどこか別
 @endprepend
 ```
 
+`@hasstack`ディレクティブは、スタックが空かを判断するために使用します。
+
+```blade
+@hasstack('list')
+    <ul>
+        @stack('list')
+    </ul>
+@endif
+```
+
 <a name="service-injection"></a>
 ## サービス注入