Someone had the same issue but didn't explain steps to solve very clearly:
Clashing migrations when upgrading to Laravel Cashier v10
Hi, I've spent about an hour upgrading my 5.7 app to ^6.0 and it all worked absolutely fine until I tried to deploy it.
For some reason it's trying to re-run a very old migration that's related to the Stripe SDK (this was also updated as part of the overall update.
Migrating: 2019_05_03_000001_create_customer_columns
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'stripe_id' (SQL: alter table `users` add `stripe_id` varchar(191) null, add `card_brand` varchar(191) null, add `card_last_f
our` varchar(4) null, add `trial_ends_at` timestamp null)
I've no idea why this old migration is trying to be processed. Anything I can do?
For anyone else who has this problem (related to upgrading Laravel Cashier to v10 from any lower version)
- Publish the migrations
php artisan vendor:publish --tag="cashier-migrations"
- Comment out any conflicting table additions (remember the up and down parts)
ps. one of the migrations tries to create a table that already exists (subscriptions) so you'll need to change that from a create migration to an update migration.
Ta
Please or to participate in this conversation.