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 nikic/php-parser to v5 #102

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nikic/php-parser ^4.17.1 -> ^5.0.2 age adoption passing confidence

Release Notes

nikic/PHP-Parser (nikic/php-parser)

v5.0.2

Compare Source

Fixed
  • Fix handling of indentation on next line after opening PHP tag in formatting-preserving pretty
    printer.
Changed
  • Avoid cyclic references in Parser objects. This means that no longer used parser objects are
    immediately destroyed now, instead of requiring cycle GC.
  • Update PhpVersion::getNewestSupported() to report PHP 8.3 instead of PHP 8.2.

v5.0.1

Compare Source

Changed
  • Added check to detect use of PHP-Parser with libraries that define T_* compatibility tokens
    with incorrect type (such as string instead of int). This would lead to TypeErrors down the
    line. Now an Error will be thrown early to indicate the problem.

v5.0.0

Compare Source

See UPGRADE-5.0 for detailed migration instructions.

Fixed
  • Fixed parent class of PropertyItem and UseItem.

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 Jan 7, 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 nikic/php-parser:5.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 nikic/php-parser ^5.0.2, found nikic/php-parser[dev-master, v5.0.2, 5.0.x-dev (alias of dev-master)] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - infection/infection is locked to version 0.27.11 and an update of this package was not requested.
    - infection/infection 0.27.11 requires nikic/php-parser ^4.15.1 -> found nikic/php-parser[v4.15.1, ..., 4.x-dev] but it conflicts with your root composer.json require (^5.0.2).
  Problem 3
    - maglnet/composer-require-checker is locked to version 4.7.1 and an update of this package was not requested.
    - maglnet/composer-require-checker 4.7.1 requires nikic/php-parser ^4.17.1 -> found nikic/php-parser[v4.17.1, ..., 4.x-dev] but it conflicts with your root composer.json require (^5.0.2).
  Problem 4
    - phpunit/php-code-coverage 10.1.14 requires nikic/php-parser ^4.18 || ^5.0 -> found nikic/php-parser[dev-master, v4.18.0, v4.19.0, v4.19.1, 4.x-dev, v5.0.0alpha1, ..., 5.0.x-dev (alias of dev-master)] but these were not loaded, likely because it conflicts with another require.
    - phpunit/phpunit 10.5.20 requires phpunit/php-code-coverage ^10.1.5 -> satisfiable by phpunit/php-code-coverage[10.1.14].
    - phpunit/phpunit is locked to version 10.5.20 and an update of this package was not requested.

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 Jan 7, 2024
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 6 times, most recently from 51e7f12 to dcb546e Compare January 14, 2024 16:23
@renovate renovate bot changed the base branch from 1.11.x to 1.12.x January 14, 2024 19:23
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from 29f0525 to d8a49f4 Compare January 20, 2024 04:36
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 2 times, most recently from bae2e95 to 76053d4 Compare January 25, 2024 03:08
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 4 times, most recently from 98ba2c3 to 401485a Compare February 8, 2024 04:37
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 2 times, most recently from 99dc963 to a40a005 Compare February 17, 2024 05:05
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 5 times, most recently from cfced29 to 4bbcb78 Compare February 26, 2024 04:24
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from 4f2bf8e to 6a80a50 Compare March 5, 2024 22:27
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 2 times, most recently from 26dfa8f to be64d72 Compare March 10, 2024 04:16
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 5 times, most recently from 76b1833 to 34817b8 Compare March 24, 2024 04:54
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from 5e22916 to d877a3e Compare April 1, 2024 03:50
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from ac1e144 to 87a5557 Compare April 7, 2024 03:22
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 4 times, most recently from 41df4f8 to 78ff058 Compare April 20, 2024 04:45
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from 49e1748 to 9e3b249 Compare April 30, 2024 04:43
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 2 times, most recently from 4f478da to d38ca90 Compare May 7, 2024 04:52
Copy link
Contributor Author

renovate bot commented May 14, 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 nikic/php-parser:5.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 nikic/php-parser ^5.0.2, found nikic/php-parser[dev-master, v5.0.2, 5.0.x-dev (alias of dev-master)] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - infection/infection is locked to version 0.27.11 and an update of this package was not requested.
    - infection/infection 0.27.11 requires nikic/php-parser ^4.15.1 -> found nikic/php-parser[v4.15.1, ..., 4.x-dev] but it conflicts with your root composer.json require (^5.0.2).
  Problem 3
    - maglnet/composer-require-checker is locked to version 4.7.1 and an update of this package was not requested.
    - maglnet/composer-require-checker 4.7.1 requires nikic/php-parser ^4.17.1 -> found nikic/php-parser[v4.17.1, ..., 4.x-dev] but it conflicts with your root composer.json require (^5.0.2).
  Problem 4
    - phpunit/php-code-coverage 10.1.14 requires nikic/php-parser ^4.18 || ^5.0 -> found nikic/php-parser[dev-master, v4.18.0, v4.19.0, v4.19.1, 4.x-dev, v5.0.0alpha1, ..., 5.0.x-dev (alias of dev-master)] but these were not loaded, likely because it conflicts with another require.
    - phpunit/phpunit 10.5.20 requires phpunit/php-code-coverage ^10.1.5 -> satisfiable by phpunit/php-code-coverage[10.1.14].
    - phpunit/phpunit is locked to version 10.5.20 and an update of this package was not requested.

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/nikic-php-parser-5.x branch 2 times, most recently from a1bf95d to b35e04a Compare May 19, 2024 04:41
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 3 times, most recently from 71eda60 to 2fe8f01 Compare May 28, 2024 04:30
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch 2 times, most recently from 9dbd3a6 to 803b037 Compare June 3, 2024 04:46
| datasource | package          | from   | to    |
| ---------- | ---------------- | ------ | ----- |
| packagist  | nikic/php-parser | 4.19.1 | 5.0.2 |
@renovate renovate bot force-pushed the renovate/nikic-php-parser-5.x branch from 803b037 to e48e9ed Compare June 7, 2024 03:41
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.

None yet

0 participants