⬆️ Update dependency pestphp/pest to v4.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pestphp/pest	4.4.6 → 4.7.0

---

Release Notes

pestphp/pest (pestphp/pest)

v4.7.0

Compare Source

• maintenance release

v4.6.3

Compare Source

chore: bumps phpunit

v4.6.2

Compare Source

fix: bumps phpunit, as previous versions became invalid due GHSA-qrr6-mg7r-m243

v4.6.1

Compare Source

• fix: up to 30% faster boot times before your test suite runs (measured on laravel cloud)
• fix: if you pass --filter or a test file, --update-snapshots now only updates the snapshots that match

v4.6.0

Compare Source

• feat: time based sharding by @​nunomaduro in #​1671

For better shard balance, Pest can distribute tests based on their actual execution time using the --update-shards option. This ensures each shard takes roughly the same wall-clock time, minimizing how long your slowest CI job runs.

Step 1: Generate the timing data by running your full test suite with --update-shards:

./vendor/bin/pest --update-shards

This runs all tests and records each test class's duration into tests/.pest/shards.json. You can also combine it with --parallel to speed things up:

./vendor/bin/pest --parallel --update-shards

Step 2: Commit tests/.pest/shards.json to your repository. This file is human-readable and looks like this:

{
    "timings": {
        "Tests\\Feature\\Payments\\StripeCheckoutTest": 1.608,
        "Tests\\Feature\\Reports\\SalesReportTest": 2.105,
        "Tests\\Unit\\Models\\UserTest": 0.050
    },
    "checksum": "...",
    "updated_at": "2026-04-14T10:30:00+00:00"
}

Step 3: When you run --shard and tests/.pest/shards.json exists, Pest automatically uses time-balanced distribution:

./vendor/bin/pest --shard=1/5

The output will indicate that time-balanced sharding is active:

Shard:    1 of 5 — 12 files ran, out of 50 (time-balanced).

v4.5.0

Compare Source

Announcement: x.com/enunomaduro/status/2042697927483609449

• feat: flaky and --flaky by @​nunomaduro
• feat: toBeCasedCorrectly arch test assertion by @​SimonBroekaert and @​nunomaduro in #​1455
• feat: add '--only-covered' option to '--coverage' by @​SimonBroekaert in #​1626
• fix: typo in Pest.php in stubs by @​orphanedrecord in #​1653
• fix: toUseTrait to detect inherited and nested traits by @​yondifon in #​1515
• fix: missing classes before toExtend on laravel preset by @​treyssatvincent in #​1569
• fix: add "Rules" to laravel preset by @​bibrokhim in #​1580
• fix: enhance support for --parallel and --teamcity arguments by restoring --teamcity for ParaTest and fixing teamcity output concurrency by @​smirok in #​1615
• fix: nested dataset discovery and parallel invalid-dataset reporting by @​stsepelin in #​1655
• fix: preserve unicode characters in filenames for --filter matching by @​Vmadmax in #​1624
• fix: dataset named parameters by @​dbpolito in #​1634
• fix: parameter closure this type annotations in functions by @​DevDavido in #​1628
• fix: dataset inheritance with method chaining (beforeEach()->with(), describe()->with()) by @​louisbels in #​1565

---

Configuration

📅 Schedule: (in timezone Europe/Amsterdam)

• Branch creation
  • "before 6am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: composer update pestphp/pest:4.7.0 --with-dependencies --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Dependency nunomaduro/collision is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires pestphp/pest ^4.0 -> satisfiable by pestphp/pest[v4.7.0].
    - pestphp/pest v4.7.0 requires nunomaduro/collision ^8.9.4 -> found nunomaduro/collision[v8.9.4] but the package is fixed to v8.9.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
  Problem 2
    - pestphp/pest-plugin-laravel is locked to version v4.1.0 and an update of this package was not requested.
    - pestphp/pest v4.7.0 requires nunomaduro/collision ^8.9.4 -> found nunomaduro/collision[v8.9.4] but the package is fixed to v8.9.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - pestphp/pest-plugin-laravel v4.1.0 requires pestphp/pest ^4.4.1 -> satisfiable by pestphp/pest[v4.7.0].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.