Skip to content

chore(deps): lock file maintenance#8

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/lock-file-maintenance
Open

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

Conversation

@renovate

@renovate renovate Bot commented Aug 3, 2024

Copy link
Copy Markdown

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: (UTC)

  • Branch creation
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 added the dependencies label Aug 3, 2024
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from dc291f5 to 4b0fe4b Compare August 19, 2024 07:53
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 62034ed to f175c52 Compare August 14, 2025 11:03
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from f175c52 to 1a3c1dc Compare August 19, 2025 19:42
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 1a3c1dc to 7d5e865 Compare August 31, 2025 10:53
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 7d5e865 to 105fe5f Compare September 25, 2025 21:42
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 105fe5f to 98d017e Compare October 22, 2025 01:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 98d017e to c88f3d4 Compare November 11, 2025 00:10
@renovate

renovate Bot commented Nov 18, 2025

Copy link
Copy Markdown
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 laravel/framework 11.18.1 (exact version match: 11.18.1 or 11.18.1.0), found laravel/framework[v11.18.1] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-q46n-4fdk-zjr4", "PKSA-qzrn-rnz3-85w1", "PKSA-w7xr-vk7n-rstm"). 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 phpunit/phpunit 11.2.8 (exact version match: 11.2.8 or 11.2.8.0), found phpunit/phpunit[11.2.8] 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 3
    - Root composer.json requires laravel/octane 2.5.2 -> satisfiable by laravel/octane[v2.5.2].
    - laravel/octane v2.5.2 requires laravel/framework ^10.10.1|^11.0 -> found laravel/framework[v10.10.1, ..., 10.50.2, v11.0.0, ..., v11.54.0] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-q46n-4fdk-zjr4", "PKSA-qzrn-rnz3-85w1", "PKSA-w7xr-vk7n-rstm"). 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 laravel/passport 12.2.1 -> satisfiable by laravel/passport[v12.2.1].
    - laravel/passport v12.2.1 requires firebase/php-jwt ^6.4 -> found firebase/php-jwt[v6.4.0, ..., v6.11.1] but these were not loaded, because they are affected by security advisories ("PKSA-y2cr-5h3j-g3ys"). 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 5
    - Root composer.json requires openai-php/laravel 0.10.1 -> satisfiable by openai-php/laravel[v0.10.1].
    - openai-php/laravel v0.10.1 requires laravel/framework ^9.46.0|^10.34.2|^11.0 -> found laravel/framework[v9.46.0, ..., v9.52.21, v10.34.2, ..., 10.50.2, v11.0.0, ..., v11.54.0] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-q46n-4fdk-zjr4", "PKSA-qzrn-rnz3-85w1", "PKSA-w7xr-vk7n-rstm"). 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.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants