From a27117afdd8b28d079d26aa504508a67477d7115 Mon Sep 17 00:00:00 2001 From: lupinitylabs Date: Thu, 20 Oct 2022 06:51:03 +0200 Subject: [PATCH 1/2] add support for laravel/sanctum ^3.0 --- composer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/composer.json b/composer.json index fddb859..84892b1 100644 --- a/composer.json +++ b/composer.json @@ -29,7 +29,7 @@ "guzzlehttp/guzzle": "^7.4", "illuminate/support": "^8.0|^9.0", "laravel/framework": "^8.0|^9.0", - "laravel/sanctum": "^2.4", + "laravel/sanctum": "^2.4|^3.0", "ext-pdo": "*" }, "require-dev": { From 93bb82d3c35339593670c8dd32440350de599900 Mon Sep 17 00:00:00 2001 From: Gael Connan Date: Mon, 24 Oct 2022 16:57:04 +0200 Subject: [PATCH 2/2] update the 2.x migration guide in the readme. --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index aba3f16..35a444b 100644 --- a/README.md +++ b/README.md @@ -262,6 +262,13 @@ See [cybex-gmbh/collector](https://github.com/cybex-gmbh/collector) for an examp ## Migration guide from Protector v1.x to v2.x +Likelihood of impact: high + +- If your app does not explicitly require the laravel/sanctum package, upgrading Protector to version 2.x may also +upgrade Sanctum to version 3.x. This will require you to follow its +[upgrade guide](https://github.com/laravel/sanctum/blob/3.x/UPGRADE.md). Alternatively you can explicitly require +laravel/sanctum ^2.4 in your app to lock its version. + Likelihood of impact: low - Access to the formerly public methods getGitRevision(), getGitHeadDate() or getGitBranch() is now protected.