Updating an Existing Project to Craft 3.7 Beta

The best way to test Craft 3.7 beta in an exist­ing project is to cre­ate a new Git branch local­ly, clone the local data­base and update the .env file to point to the new data­base. This way, you iso­late the Craft 3.7 beta entire­ly from any oth­er local devel­op­ment work you have going on.

Once you do that, update the composer.json file for the project and change the ver­sion of Craft to ^3.7.0-beta.1.

"craftcms/cms": "^3.7.0-beta.1",

This SemVer string will get you the beta 1 and every­thing that comes after it until 3.8.0.

To get the beta ver­sion of Craft, update Com­pos­er in the project to pull down the lat­est dependencies.

$ composer update

You should see the 3.6.x to 3.7.0‑beta.1 update print­ed out to the screen.

The final step is to update the data­base with any changes required by 3.7 beta using the migra­tions command.

$ php craft migrate/all

If you’re run­ning Nitro, then you’ll use:

$ nitro craft migrate/all

You can also sim­ply open up the Craft con­trol pan­el for the project and it will prompt you to run the migrations.