Bump pestphp/pest from 4.5.0 to 4.6.3

[dependabot]

Bumps pestphp/pest from 4.5.0 to 4.6.3.

Release notes

Sourced from pestphp/pest's releases.

v4.6.3

chore: bumps phpunit

v4.6.2

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

v4.6.1

• 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

• feat: time based sharding by @​nunomaduro in pestphp/pest#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:

</tr></table> 

... (truncated)

Commits

• bff4456 release: v4.6.3
• 9ebb990 chore: bumps phpunit
• cabff73 release: v4.6.2
• 0746173 chore: bumps phpunit
• 87db0b4 release: v4.6.1
• 6ba373a chore: bumps phpunit
• 945d476 fix: allow to update individual screenshots
• a8cf0fe chore: improves CI
• 2ae072b feat: makes boot time much faster
• 59d0669 chore: missing header
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)