Skip to content

chore(deps): update dependency pestphp/pest-plugin-laravel to v3 #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 11, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pestphp/pest-plugin-laravel ^2.3 -> ^3.0 age adoption passing confidence

Release Notes

pestphp/pest-plugin-laravel (pestphp/pest-plugin-laravel)

v3.2.0

Compare Source

v3.1.0

Compare Source

v3.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 renovate bot enabled auto-merge (squash) May 11, 2025 05:37
Copy link
Contributor Author

renovate bot commented May 11, 2025

⚠️ 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-plugin-laravel:3.2.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 laravel/framework 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.
Dependency pestphp/pest 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
    - ergebnis/composer-normalize is locked to version 2.42.0 and an update of this package was not requested.
    - ergebnis/composer-normalize 2.42.0 requires php ~7.4.0 || ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.4.7) does not satisfy that requirement.
  Problem 2
    - Root composer.json requires pestphp/pest-plugin-laravel ^3.0 -> satisfiable by pestphp/pest-plugin-laravel[v3.2.0].
    - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., v11.44.7, v12.9.2, ..., v12.13.0] but it conflicts with your root composer.json require (^v10.46).
  Problem 3
    - pestphp/pest is locked to version v2.34.7 and an update of this package was not requested.
    - brianium/paratest v7.4.3 requires php ~8.2.0 || ~8.3.0 -> your php version (8.4.7) does not satisfy that requirement.
    - pestphp/pest v2.34.7 requires brianium/paratest ^7.3.1 -> satisfiable by brianium/paratest[v7.4.3].

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants