Laravel Deploy Operations 7.x Help

Upgrading To 4.x from 3.x

High-Impact Changes

  1. Updating Dependencies

  2. Rename package name

  3. Changing the names of console commands

Minor-Impact Changes

Low-Impact Changes

The easiest way to upgrade

For your convenience, we have created an `upgrade` console command:

composer remove dragon-code/laravel-migration-actions composer require dragon-code/laravel-actions:^4.0 php artisan actions:upgrade php artisan migrate

It will do the following:

  • Renaming manually invoked commands in a project to a new name

Updating Dependencies

Rename package name

You should update the following dependency in your application's composer.json file:

Replace:

{ "require": { "dragon-code/laravel-migration-actions": "^3.0" } }

with:

{ "require": { "dragon-code/laravel-actions": "^4.0" } }

Then you need to update the dependencies:

composer update

Changing the names of console commands

New Name

Old Name

php artisan make:action

php artisan make:migration:action

php artisan actions

php artisan migrate:actions

php artisan actions:install

php artisan migrate:actions:install

php artisan actions:fresh

php artisan migrate:actions:fresh

php artisan actions:refresh

php artisan migrate:actions:refresh

php artisan actions:reset

php artisan migrate:actions:reset

php artisan actions:rollback

php artisan migrate:actions:rollback

php artisan actions:status

php artisan migrate:actions:status

php artisan actions:upgrade

php artisan migrate:actions:upgrade

Names::MIGRATE constant name changed

Replace DragonCode\LaravelActions\Constants\Names::MIGRATE with DragonCode\LaravelActions\Constants\Names::ACTIONS

Changed the default name of the table for storing actions

The new table name is `actions`.

You can also specify any name in the application settings file.

02 April 2025