Skip to content

fix(deps): update dependency laravel/sanctum to v4#142

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/laravel-sanctum-4.x
Open

fix(deps): update dependency laravel/sanctum to v4#142
renovate[bot] wants to merge 1 commit intomainfrom
renovate/laravel-sanctum-4.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2024

This PR contains the following updates:

Package Change Age Confidence
laravel/sanctum ^3.0^4.0 age confidence

Release Notes

laravel/sanctum (laravel/sanctum)

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.4

Compare Source

v4.2.3

Compare Source

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

  • Fixes inconsistency in Sanctum::currentApplicationUrlWithPort() and Sanctum::currentRequestHost() by @​denjaland in #​565

v4.1.0

Compare Source

v4.0.8

Compare Source

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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
Copy link
Contributor Author

renovate bot commented Mar 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 laravel/sanctum:4.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
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
    - Root composer.json requires laravel/sanctum ^4.0 -> satisfiable by laravel/sanctum[v4.0.2].
    - laravel/sanctum v4.0.2 requires illuminate/console ^11.0 -> found illuminate/console[v11.0.0, ..., v11.6.0] 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/laravel-sanctum-4.x branch 3 times, most recently from bec04c7 to 2fba1f3 Compare March 21, 2024 09:50
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 5 times, most recently from e94fd74 to d0941d7 Compare March 28, 2024 17:15
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 3 times, most recently from 80cb724 to 30c5ac7 Compare April 6, 2024 09:04
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch from 30c5ac7 to ec2f10e Compare April 14, 2024 11:45
@coderabbitai
Copy link

coderabbitai bot commented Apr 14, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 4 times, most recently from d36980c to f89ede9 Compare April 30, 2024 19:09
@renovate
Copy link
Contributor Author

renovate bot commented May 16, 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/sanctum:4.3.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
    - Root composer.json requires laravel/sanctum ^4.0 -> satisfiable by laravel/sanctum[v4.3.1].
    - laravel/sanctum v4.3.1 requires illuminate/console ^11.0|^12.0|^13.0 -> found illuminate/console[v11.0.0, ..., v11.47.0, v12.0.0, ..., v12.51.0] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - laravel-lang/common is locked to version v4.0.0 and an update of this package was not requested.
    - laravel-lang/common v4.0.0 requires laravel-lang/publisher ^14.6.4 -> satisfiable by laravel-lang/publisher[v14.7.0].
    - laravel-lang/publisher v14.7.0 requires league/config ^1.2 -> satisfiable by league/config[v1.2.0].
    - league/config v1.2.0 requires nette/schema ^1.2 -> satisfiable by nette/schema[v1.3.2].
    - nette/schema v1.3.2 requires php 8.1 - 8.4 -> your php version (8.5.2) does not satisfy that requirement.

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/laravel-sanctum-4.x branch 3 times, most recently from cb6e638 to bc105e1 Compare May 22, 2024 14:42
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 3 times, most recently from cb7ee07 to 5eef2fb Compare June 13, 2024 12:31
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 4 times, most recently from e120a60 to 93c6539 Compare June 19, 2024 10:52
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 2 times, most recently from 3e14de0 to 2b958ec Compare August 1, 2025 12:07
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 5 times, most recently from dde1d3d to 032fe10 Compare August 16, 2025 08:42
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 3 times, most recently from b28b995 to 59c9550 Compare August 26, 2025 22:34
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 2 times, most recently from 4ffc77b to 0b01178 Compare September 3, 2025 13:52
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 4 times, most recently from e40d7b5 to adff238 Compare September 17, 2025 05:50
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 5 times, most recently from 68c0542 to 4c29936 Compare September 24, 2025 13:57
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 3 times, most recently from 32352b7 to 4d0064f Compare October 3, 2025 08:47
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch from 4d0064f to 8c2f148 Compare October 9, 2025 22:08
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch 2 times, most recently from 9925c38 to fa74e30 Compare October 30, 2025 23:56
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch from fa74e30 to 05b84d4 Compare November 13, 2025 02:07
@renovate renovate bot force-pushed the renovate/laravel-sanctum-4.x branch from 05b84d4 to cc91561 Compare November 13, 2025 20:52
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.

0 participants