Update dependency pestphp/pest to v5 #113
No reviewers
Labels
No labels
0Type
Dependencies
1Dependency
Composer
1Dependency
NPM
2Dependency-Impact
Major
2Dependency-Impact
Minor
2Dependency-Impact
Patch
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
l4p1n-bot/website!113
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/pestphp-pest-5.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^4.0→^5.0Release Notes
pestphp/pest (pestphp/pest)
v5.0.2Compare Source
--helpby @talaridisTh in #1780v5.0.1Compare Source
fix: missing laravel boost skill by @pushpak1300 in #1775
v5.0.0Compare Source
say hello to pest v5
· tia: the fastest testing engine in the world
· agent browser plugin: 10x better than the rest
· phpstan + rector: built in
· evals: test your agents
announcement: pestphp.com/docs/pest5-now-available
v4.7.7Compare Source
--tiahidden codev4.7.5Compare Source
v4.7.4Compare Source
actions/checkoutfrom6.0.3to7.0.0v4.7.3Compare Source
ddoutput on parallel testingv4.7.2Compare Source
v4.7.1Compare Source
v4.7.0Compare Source
v4.6.3Compare Source
chore: bumps phpunit
v4.6.2Compare Source
fix: bumps phpunit, as previous versions became invalid due https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-qrr6-mg7r-m243
v4.6.1Compare Source
v4.6.0Compare Source
For better shard balance, Pest can distribute tests based on their actual execution time using the
--update-shardsoption. 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:This runs all tests and records each test class's duration into
tests/.pest/shards.json. You can also combine it with--parallelto speed things up:Step 2: Commit
tests/.pest/shards.jsonto your repository. This file is human-readable and looks like this:Step 3: When you run
--shardandtests/.pest/shards.jsonexists, Pest automatically uses time-balanced distribution:The output will indicate that time-balanced sharding is active:
v4.5.0Compare Source
Announcement: x.com/enunomaduro/status/2042697927483609449
flakyand--flakyby @nunomadurotoBeCasedCorrectlyarch test assertion by @SimonBroekaert and @nunomaduro in #1455Pest.phpin stubs by @orphanedrecord in #1653toUseTraitto detect inherited and nested traits by @yondifon in #1515toExtendonlaravelpreset by @treyssatvincent in #1569laravelpreset by @bibrokhim in #1580--paralleland--teamcityarguments by restoring--teamcityfor ParaTest and fixing teamcity output concurrency by @smirok in #1615--filtermatching by @Vmadmax in #1624v4.4.6Compare Source
paoConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
⚠️ 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:
The artifact failure details are included below:
File name: composer.lock
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.