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

Update dependency phing/phing to v3 #540

Open
wants to merge 1 commit into
base: 4.15.x
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
phing/phing (source) ^2.17.4 -> ^3.0.0 age adoption passing confidence

Release Notes

phingofficial/phing (phing/phing)

v3.0.0

Compare Source

Finally, the first stable release of Phing 3.0 is here!

Please refer to the upgrade guide to read all about (backwards incompatible) changes from Phing 2.0 to Phing 3.0.

The following issues and pull requests were closed in this release:

  • Fix(php-cs-fixer.dist.php): Use absolute paths from DIR #​1819
  • gitdescribe outputProperty spurious EOL character captured in property #​1814
  • Property File Loading Order and Variable Reference Issue #​1784
  • Found unconstructed IntlDateFormatter #​1783
  • Add a passthru attribute to PHPStanTask so it can print errors #​1767

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

Read more about the use of Renovate Bot within ocramius/* projects.

Copy link
Contributor Author

renovate bot commented May 3, 2024

⚠ 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 phing/phing:3.0.0 --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 symfony/console 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 phing/phing ^3.0.0 -> satisfiable by phing/phing[3.0.0].
    - phing/phing 3.0.0 requires symfony/console ^5.3.10|^6.0 -> found symfony/console[v5.3.10, ..., v5.4.39, v6.0.0, ..., v6.4.7] but the package is fixed to v7.0.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

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

@renovate renovate bot added the renovate label May 3, 2024
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 3 times, most recently from 59c7344 to 8641424 Compare May 7, 2024 05:07
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch from 8641424 to c182af5 Compare May 13, 2024 10:34
Copy link
Contributor Author

renovate bot commented May 13, 2024

⚠️ 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 phing/phing:3.0.0 --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 symfony/console 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 phing/phing ^3.0.0 -> satisfiable by phing/phing[3.0.0].
    - phing/phing 3.0.0 requires symfony/console ^5.3.10|^6.0 -> found symfony/console[v5.3.10, ..., v5.4.47, v6.0.0, ..., v6.4.15] but the package is fixed to v7.1.8 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

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/phing-phing-3.x branch 2 times, most recently from 0af75eb to fb27853 Compare May 21, 2024 12:37
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 3 times, most recently from 5305037 to a20e125 Compare May 28, 2024 05:12
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 5 times, most recently from cd28004 to 9bd7a8c Compare June 6, 2024 15:22
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 6 times, most recently from 797f02f to f008b95 Compare June 20, 2024 00:38
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 4 times, most recently from 697bcac to 32ac895 Compare June 24, 2024 10:58
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 3 times, most recently from 66d1d60 to a541855 Compare July 1, 2024 20:24
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 4 times, most recently from 9214d6f to 6f55d0d Compare October 3, 2024 03:41
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 2 times, most recently from 6adc0a9 to 3ced5f7 Compare October 8, 2024 19:15
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 2 times, most recently from a3f5ad6 to 0809a72 Compare October 18, 2024 08:09
@renovate renovate bot changed the base branch from 4.13.x to 4.14.x October 18, 2024 10:47
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 3 times, most recently from 6035c4c to 1ab116a Compare October 19, 2024 16:47
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 2 times, most recently from 2e06f2e to 1d5a78f Compare October 28, 2024 19:41
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 7 times, most recently from 6dc7150 to e3fcae2 Compare November 10, 2024 22:06
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 2 times, most recently from da72522 to 72fcab5 Compare November 13, 2024 02:00
@renovate renovate bot changed the base branch from 4.14.x to 4.15.x November 13, 2024 05:28
@renovate renovate bot force-pushed the renovate/phing-phing-3.x branch 4 times, most recently from eb08ad6 to 806a289 Compare November 17, 2024 19:47
| datasource | package     | from   | to    |
| ---------- | ----------- | ------ | ----- |
| packagist  | phing/phing | 2.17.4 | 3.0.0 |
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.

1 participant