Skip to content

chore(deps): lock file maintenance - #613

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Closed

chore(deps): lock file maintenance#613
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented May 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "before 4am on monday"
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 commented May 8, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 --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 10.5.27 (exact version match: 10.5.27 or 10.5.27.0), found phpunit/phpunit[10.5.27] but these were not loaded, because they are affected by security advisories ("PKSA-z3gr-8qht-p93v"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 2
    - Root composer.json requires squizlabs/php_codesniffer 3.10.1 (exact version match: 3.10.1 or 3.10.1.0), found squizlabs/php_codesniffer[3.10.1] but these were not loaded, because they are affected by security advisories ("PKSA-rdkp-vv9z-mjkg"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 3
    - Root composer.json requires wp-coding-standards/wpcs 2.3.0 (exact version match: 2.3.0 or 2.3.0.0), found wp-coding-standards/wpcs[2.3.0] but these were not loaded, because they are affected by security advisories ("PKSA-mh9b-91zm-m1gy"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 4
    - Root composer.json requires phpcompatibility/phpcompatibility-wp 2.1.5 -> satisfiable by phpcompatibility/phpcompatibility-wp[2.1.5].
    - phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5] require squizlabs/php_codesniffer ^2.3 || ^3.0.2 -> found squizlabs/php_codesniffer[2.3.0, ..., 2.9.2, 3.0.2, ..., 3.13.6] but these were not loaded, because they are affected by security advisories ("PKSA-rdkp-vv9z-mjkg", "PKSA-6vdd-n4sx-knhy"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
    - phpcompatibility/phpcompatibility-wp 2.1.5 requires phpcompatibility/php-compatibility ^9.0 -> satisfiable by phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5].


@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 2d6d2cc to 6805e67 Compare May 18, 2026 12:29
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from e3ea4ff to ed6a1fa Compare June 1, 2026 22:05
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from ed6a1fa to 9ada850 Compare June 11, 2026 15:50
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from feeecf0 to 05484dd Compare July 16, 2026 16:12
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 4e62007 to e676c53 Compare July 24, 2026 21:29
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from cdb7087 to 5339d37 Compare August 4, 2026 19:10
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5339d37 to e2ee8ae Compare August 12, 2026 00:15
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from e2ee8ae to 66a3a48 Compare August 14, 2026 21:55
@mirucon

mirucon commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Closing leftover Renovate PR after switching this repo to dependencyDashboardApproval. Updates will stay on the dashboard until explicitly created.

@mirucon mirucon closed this Aug 15, 2026
@mirucon
mirucon deleted the renovate/lock-file-maintenance branch August 15, 2026 10:22
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.

1 participant