Skip to content

Update dependency nunomaduro/collision to v8 #266

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 5, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nunomaduro/collision 6.4.0 -> 8.8.2 age adoption passing confidence

Release Notes

nunomaduro/collision (nunomaduro/collision)

v8.8.2

Compare Source

v8.8.1

Compare Source

v8.8.0

Compare Source

v8.7.0

Compare Source

v8.6.1

Compare Source

v8.6.0

Compare Source

v8.5.0

Compare Source

v8.4.0

Compare Source

v8.3.0

Compare Source

v8.1.1

Compare Source

v8.1.0

Compare Source

v8.0.1

Compare Source

v8.0.0

Compare Source

v7.12.0

Compare Source

v7.11.0

Compare Source

v7.10.0

Compare Source

v7.9.0

Compare Source

v7.8.1

Compare Source

v7.8.0

Compare Source

v7.7.0

Compare Source

v7.6.0

Compare Source

v7.5.2

Compare Source

v7.5.1

Compare Source

v7.5.0

Compare Source

v7.4.0

Compare Source

v7.3.3

Compare Source

v7.3.2

Compare Source

v7.3.1

Compare Source

v7.3.0

Compare Source

v7.2.0

Compare Source

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

v7.0.5

Compare Source

v7.0.4

Compare Source

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the update Update of the dependencies of the project label Dec 5, 2023
Copy link
Contributor Author

renovate bot commented Dec 5, 2023

⚠ 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 nunomaduro/collision:8.1.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
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires nunomaduro/collision 8.1.1 -> satisfiable by nunomaduro/collision[v8.1.1].
    - nunomaduro/collision v8.1.1 requires nunomaduro/termwind ^2.0.1 -> found nunomaduro/termwind[v2.0.1, 2.x-dev] but these were not loaded, likely because it conflicts with another require.

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/nunomaduro-collision-8.x branch 6 times, most recently from 8607cb8 to f3b115c Compare December 9, 2023 12:47
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from f3b115c to cef3ec1 Compare December 22, 2023 19:11
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from cef3ec1 to bbdebbe Compare January 12, 2024 17:14
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 11 times, most recently from a78bd5a to 32f95a9 Compare February 4, 2024 02:15
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from 32f95a9 to 681969a Compare February 12, 2024 21:41
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 8 times, most recently from 5c668e6 to 3c5d71c Compare March 13, 2024 12:57
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 6 times, most recently from 65d6526 to 6ab1c26 Compare November 27, 2024 15:51
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 2 times, most recently from 7873aed to af43746 Compare January 23, 2025 16:56
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 9 times, most recently from ab0c652 to ef19e22 Compare February 26, 2025 10:02
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from ef19e22 to fbbbdcd Compare March 15, 2025 02:08
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from fbbbdcd to 28755c2 Compare April 3, 2025 15:10
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from 28755c2 to cf38a95 Compare June 11, 2025 03:23
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from cf38a95 to cd327e4 Compare June 25, 2025 03:42
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch 7 times, most recently from 1b749c1 to 01adbf2 Compare July 3, 2025 21:27
@renovate renovate bot force-pushed the renovate/nunomaduro-collision-8.x branch from 01adbf2 to e918134 Compare July 4, 2025 03:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
update Update of the dependencies of the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants