Skip to content
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

chore(deps): update dependency phpunit/phpunit to v12 #6822

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
phpunit/phpunit (source) 11.5.7 -> 12.0.2 age adoption passing confidence

Release Notes

sebastianbergmann/phpunit (phpunit/phpunit)

v12.0.2

Compare Source

v12.0.1

Compare Source

v12.0.0

Compare Source


Configuration

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

🚦 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.


  • 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 added the renovate label Feb 7, 2025
Copy link
Contributor Author

renovate bot commented Feb 7, 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: api/composer.lock
Command failed: composer update phpunit/phpunit:12.0.2 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires phpunit/phpunit 12.0.2 (exact version match: 12.0.2 or 12.0.2.0), found phpunit/phpunit[12.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - brianium/paratest is locked to version v7.8.0 and an update of this package was not requested.
    - brianium/paratest v7.8.0 requires phpunit/phpunit ^11.5.7 || ^12.0.1 -> found phpunit/phpunit[11.5.7, 12.0.1, 12.0.2] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - phpspec/prophecy-phpunit is locked to version v2.3.0 and an update of this package was not requested.
    - phpspec/prophecy-phpunit v2.3.0 requires phpunit/phpunit ^9.1 || ^10.1 || ^11.0 -> found phpunit/phpunit[9.1.0, ..., 9.6.22, 10.1.0, ..., 10.5.45, 11.0.0, ..., 11.5.7] but it conflicts with your root composer.json require (12.0.2).
  Problem 4
    - spatie/phpunit-snapshot-assertions is locked to version 5.1.7 and an update of this package was not requested.
    - spatie/phpunit-snapshot-assertions 5.1.7 requires phpunit/phpunit ^10.0|^11.0 -> found phpunit/phpunit[10.0.0, ..., 10.5.45, 11.0.0, ..., 11.5.7] but it conflicts with your root composer.json require (12.0.2).

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

@renovate renovate bot force-pushed the renovate/phpunit-phpunit-12.x branch 3 times, most recently from 9c8a63d to f29be8c Compare February 10, 2025 13:39
@renovate renovate bot force-pushed the renovate/phpunit-phpunit-12.x branch from f29be8c to d86d9eb Compare February 10, 2025 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants