Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 15, 2022

This PR contains the following updates:

Package Change Age Confidence
laravel/tinker 2.7.0 -> 2.10.1 age confidence

Release Notes

laravel/tinker (laravel/tinker)

v2.10.1

Compare Source

v2.10.0

Compare Source

v2.9.0

Compare Source

v2.8.2

Compare Source

v2.8.1

Compare Source

v2.8.0

Compare Source

Added
  • Laravel v10 support

v2.7.3

Compare Source

Changed

v2.7.2

Compare Source

Fixed

v2.7.1

Compare Source

Fixed

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 becomes conflicted, 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 force-pushed the renovate/laravel-tinker-2.x branch from f448f3f to 38224c1 Compare March 29, 2022 16:32
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.7.1 Update dependency laravel/tinker to v2.7.2 Mar 29, 2022
@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from 38224c1 to 3583a20 Compare November 20, 2022 16:21
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.7.2 Update dependency laravel/tinker to v2.7.3 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from 3583a20 to 58402d9 Compare March 18, 2023 06:06
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.7.3 Update dependency laravel/tinker to v2.8.1 Mar 18, 2023
@renovate
Copy link
Author

renovate bot commented Mar 18, 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 laravel/tinker:2.9.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 laravel/framework 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
    - phpspec/prophecy v1.15.0 requires php ^7.2 || ~8.0, <8.2 -> your php version (8.3.1) does not satisfy that requirement.
    - phpunit/phpunit 9.5.18 requires phpspec/prophecy ^1.12.1 -> satisfiable by phpspec/prophecy[v1.15.0].
    - phpunit/phpunit is locked to version 9.5.18 and an update of this package was not requested.


@renovate renovate bot changed the title Update dependency laravel/tinker to v2.8.1 Update dependency laravel/tinker to v2.8.2 Aug 29, 2023
@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from 58402d9 to 09b2710 Compare August 29, 2023 16:50
@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from 09b2710 to 9348759 Compare January 9, 2024 19:51
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.8.2 Update dependency laravel/tinker to v2.9.0 Jan 9, 2024
@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from 9348759 to f1d12da Compare September 24, 2024 19:47
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.9.0 Update dependency laravel/tinker to v2.10.0 Sep 24, 2024
@renovate
Copy link
Author

renovate bot commented Sep 24, 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 laravel/tinker:2.10.1 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Dependency laravel/framework 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
    - phpunit/phpunit is locked to version 9.5.18 and an update of this package was not requested.
    - phpspec/prophecy v1.15.0 requires php ^7.2 || ~8.0, <8.2 -> your php version (8.4.11) does not satisfy that requirement.
    - phpunit/phpunit 9.5.18 requires phpspec/prophecy ^1.12.1 -> satisfiable by phpspec/prophecy[v1.15.0].


@renovate renovate bot force-pushed the renovate/laravel-tinker-2.x branch from f1d12da to d056b87 Compare January 28, 2025 18:43
@renovate renovate bot changed the title Update dependency laravel/tinker to v2.10.0 Update dependency laravel/tinker to v2.10.1 Jan 28, 2025
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