2025-08-25までの原文変更点を反映。

Author: HiroKws

original-en/artisan.md

@@ -494,7 +494,7 @@ return [
         label: 'Search for a user:',
         placeholder: 'E.g. Taylor Otwell',
         options: fn ($value) => strlen($value) > 0
-            ? User::where('name', 'like', "%{$value}%")->pluck('name', 'id')->all()
+            ? User::whereLike('name', "%{$value}%")->pluck('name', 'id')->all()
             : []
     ),
 ];

original-en/authentication.md

@@ -409,7 +409,7 @@ Auth::loginUsingId(1, remember: true);
 <a name="authenticate-a-user-once"></a>
 #### Authenticate a User Once
 
-You may use the `once` method to authenticate a user with the application for a single request. No sessions or cookies will be utilized when calling this method:
+You may use the `once` method to authenticate a user with the application for a single request. No sessions or cookies will be utilized when calling this method, and the `Login` event will not be dispatched:
 
 ```php
 if (Auth::once($credentials)) {

original-en/cache.md

@@ -396,7 +396,7 @@ cache()->remember('users', $seconds, function () {
 ```
 
 > [!NOTE]
-> When testing call to the global `cache` function, you may use the `Cache::shouldReceive` method just as if you were [testing the facade](/docs/{{version}}/mocking#mocking-facades).
+> When testing calls to the global `cache` function, you may use the `Cache::shouldReceive` method just as if you were [testing the facade](/docs/{{version}}/mocking#mocking-facades).
 
 <a name="atomic-locks"></a>
 ## Atomic Locks

original-en/console-tests.md

@@ -203,7 +203,7 @@ By default, the `Illuminate\Console\Events\CommandStarting` and `Illuminate\Cons
 
 use Illuminate\Foundation\Testing\WithConsoleEvents;
 
-uses(WithConsoleEvents::class);
+pest()->use(WithConsoleEvents::class);
 
 // ...
 ```

original-en/database-testing.md

@@ -21,7 +21,7 @@ Before proceeding much further, let's discuss how to reset your database after e
 
 use Illuminate\Foundation\Testing\RefreshDatabase;
 
-uses(RefreshDatabase::class);
+pest()->use(RefreshDatabase::class);
 
 test('basic example', function () {
     $response = $this->get('/');
@@ -98,7 +98,7 @@ use Database\Seeders\OrderStatusSeeder;
 use Database\Seeders\TransactionStatusSeeder;
 use Illuminate\Foundation\Testing\RefreshDatabase;
 
-uses(RefreshDatabase::class);
+pest()->use(RefreshDatabase::class);
 
 test('orders can be created', function () {
     // Run the DatabaseSeeder...

original-en/dusk.md

@@ -53,6 +53,9 @@
 <a name="introduction"></a>
 ## Introduction
 
+> [!WARNING]
+> [Pest 4](https://pestphp.com/) now includes automated browser testing which offers significant performance and usability improvements compared to Laravel Dusk. For new projects, we recommend using Pest for browser testing.
+
 [Laravel Dusk](https://github.com/laravel/dusk) provides an expressive, easy-to-use browser automation and testing API. By default, Dusk does not require you to install JDK or Selenium on your local computer. Instead, Dusk uses a standalone [ChromeDriver](https://sites.google.com/chromium.org/driver) installation. However, you are free to utilize any other Selenium compatible driver you wish.
 
 <a name="installation"></a>
@@ -163,7 +166,7 @@ The `DatabaseMigrations` trait will run your database migrations before each tes
 use Illuminate\Foundation\Testing\DatabaseMigrations;
 use Laravel\Dusk\Browser;
 
-uses(DatabaseMigrations::class);
+pest()->use(DatabaseMigrations::class);
 
 //
 ```
@@ -199,7 +202,7 @@ The `DatabaseTruncation` trait will migrate your database on the first test in o
 use Illuminate\Foundation\Testing\DatabaseTruncation;
 use Laravel\Dusk\Browser;
 
-uses(DatabaseTruncation::class);
+pest()->use(DatabaseTruncation::class);
 
 //
 ```
@@ -357,7 +360,7 @@ use App\Models\User;
 use Illuminate\Foundation\Testing\DatabaseMigrations;
 use Laravel\Dusk\Browser;
 
-uses(DatabaseMigrations::class);
+pest()->use(DatabaseMigrations::class);
 
 test('basic example', function () {
     $user = User::factory()->create([
@@ -2474,7 +2477,7 @@ use Illuminate\Foundation\Testing\DatabaseMigrations;
 use Laravel\Dusk\Browser;
 use Tests\Browser\Components\DatePicker;
 
-uses(DatabaseMigrations::class);
+pest()->use(DatabaseMigrations::class);
 
 test('basic example', function () {
     $this->browse(function (Browser $browser) {

original-en/eloquent-collections.md

@@ -335,7 +335,13 @@ class User extends Model
      */
     public function newCollection(array $models = []): Collection
     {
-        return new UserCollection($models);
+        $collection = new UserCollection($models);
+
+        if (Model::isAutomaticallyEagerLoadingRelationships()) {
+            $collection->withRelationshipAutoloading();
+        }
+
+        return $collection;
     }
 }
 ```

original-en/eloquent-serialization.md

@@ -131,16 +131,20 @@ class User extends Model
 <a name="temporarily-modifying-attribute-visibility"></a>
 #### Temporarily Modifying Attribute Visibility
 
-If you would like to make some typically hidden attributes visible on a given model instance, you may use the `makeVisible` method. The `makeVisible` method returns the model instance:
+If you would like to make some typically hidden attributes visible on a given model instance, you may use the `makeVisible` or `mergeVisible` methods. The `makeVisible` method returns the model instance:
 
 ```php
 return $user->makeVisible('attribute')->toArray();
+
+return $user->mergeVisible(['name', 'email'])->toArray();
 ```
 
-Likewise, if you would like to hide some attributes that are typically visible, you may use the `makeHidden` method.
+Likewise, if you would like to hide some attributes that are typically visible, you may use the `makeHidden` or `mergeHidden` methods:
 
 ```php
 return $user->makeHidden('attribute')->toArray();
+
+return $user->mergeHidden(['name', 'email'])->toArray();
 ```
 
 If you wish to temporarily override all of the visible or hidden attributes, you may use the `setVisible` and `setHidden` methods respectively:
@@ -203,11 +207,13 @@ Once the attribute has been added to the `appends` list, it will be included in
 <a name="appending-at-run-time"></a>
 #### Appending at Run Time
 
-At runtime, you may instruct a model instance to append additional attributes using the `append` method. Or, you may use the `setAppends` method to override the entire array of appended properties for a given model instance:
+At runtime, you may instruct a model instance to append additional attributes using the `append` or `mergeAppends` methods. Or, you may use the `setAppends` method to override the entire array of appended properties for a given model instance:
 
 ```php
 return $user->append('is_admin')->toArray();
 
+return $user->mergeAppends(['is_admin', 'status'])->toArray();
+
 return $user->setAppends(['is_admin'])->toArray();
 ```
 

original-en/facades.md

@@ -257,7 +257,7 @@ use App\Models\Podcast;
 use Facades\App\Contracts\Publisher;
 use Illuminate\Foundation\Testing\RefreshDatabase;
 
-uses(RefreshDatabase::class);
+pest()->use(RefreshDatabase::class);
 
 test('podcast can be published', function () {
     $podcast = Podcast::factory()->create();

original-en/helpers.md

@@ -73,6 +73,7 @@ Laravel includes a variety of global "helper" PHP functions. Many of these funct
 [Arr::prepend](#method-array-prepend)
 [Arr::prependKeysWith](#method-array-prependkeyswith)
 [Arr::pull](#method-array-pull)
+[Arr::push](#method-array-push)
 [Arr::query](#method-array-query)
 [Arr::random](#method-array-random)
 [Arr::reject](#method-array-reject)
@@ -959,6 +960,21 @@ use Illuminate\Support\Arr;
 $value = Arr::pull($array, $key, $default);
 ```
 
+<a name="method-array-push"></a>
+#### `Arr::push()` {.collection-method}
+
+The `Arr::push` method pushes an item into an array using "dot" notation. If an array does not exist at the given key, it will be created:
+
+```php
+use Illuminate\Support\Arr;
+
+$array = [];
+
+Arr::push($array, 'office.furniture', 'Desk');
+
+// $array: ['office' => ['furniture' => 'Desk']]
+```
+
 <a name="method-array-query"></a>
 #### `Arr::query()` {.collection-method}