Update dependency allure-framework/allure-phpunit to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
allure-framework/allure-phpunit (source)	^2 -> ^3

---

Release Notes

allure-framework/allure-phpunit (allure-framework/allure-phpunit)

v3.0.1

Compare Source

What's Changed

🐞 Bug Fixes

• Test method is correctly detectied with data provider (fixes #​98) by @​remorhaz in https://github.com/allure-framework/allure-phpunit/pull/99

Full Changelog: allure-framework/allure-phpunit@v3.0.0...v3.0.1

v3.0.0

Compare Source

What's Changed

🚀 New Features

• Support PHPUnit 10 by @​remorhaz in https://github.com/allure-framework/allure-phpunit/pull/86

⬆️ Dependency Updates

• Bump actions/checkout from 3.3.0 to 3.5.0 by @​dependabot in https://github.com/allure-framework/allure-phpunit/pull/92
• Bump actions/checkout from 3 to 4 by @​dependabot in https://github.com/allure-framework/allure-phpunit/pull/97

Full Changelog: allure-framework/allure-phpunit@v2.1.0...v3.0.0

---

Configuration

📅 Schedule: Branch creation - "on Monday through Thursday after 1:00am before 7:00am" in timezone Europe/Amsterdam, Automerge - "on Monday through Thursday after 1:00am before 7:00am" in timezone Europe/Amsterdam.

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

⚠️ 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 allure-framework/allure-phpunit:3.0.1 --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
Dependency phpunit/phpunit 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 allure-framework/allure-phpunit ^3, found allure-framework/allure-phpunit[v3.0.0, v3.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - magento/magento2-functional-testing-framework is locked to version 4.7.2 and an update of this package was not requested.
    - magento/magento2-functional-testing-framework 4.7.2 requires allure-framework/allure-phpunit ^2 -> found allure-framework/allure-phpunit[v2.0.0-rc.1, ..., v2.1.0] but it conflicts with your root composer.json require (^3).

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

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.