From 98fa78e76b535faf301dce7fd3e6abb81b778426 Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Fri, 19 Apr 2024 07:59:42 +0200 Subject: [PATCH] Update UPGRADE.md --- UPGRADE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UPGRADE.md b/UPGRADE.md index d32837bb..042d7212 100644 --- a/UPGRADE.md +++ b/UPGRADE.md @@ -62,7 +62,7 @@ Because of this change, the `Cashier::ignoreMigrations` method has been removed. PR: https://github.com/laravel/cashier-stripe/pull/1620 -To better indicate the purpose of this column, we've rename the `name` column on the `subscriptions` table to `type`. The purpose of this change is to resolve confusion surrouding the `name` column as many users believed it needed to be a customer-facing, user friendly "name", when in reality the column is mainly used to differentiate the different "types" of subscriptions your application may offer and is only used internally by Cashier. You should define the following schema change in a migration when upgrading: +To better indicate the purpose of this column, we've renamed the `name` column on the `subscriptions` table to `type`. The purpose of this change is to resolve confusion surrouding the `name` column as many users believed it needed to be a customer-facing, user friendly "name", when in reality the column is mainly used to differentiate the different "types" of subscriptions your application may offer and is only used internally by Cashier. You should define the following schema change in a migration when upgrading: ```php Schema::table('subscriptions', function (Blueprint $table) {