Creating a New Project Based on an Unstable Symfony Version¶

Suppose that the Symfony 4.0 version hasn’t been released yet and you want to create a new project to test its features. First, install the Composer package manager. Then, open a command console, enter your project’s directory and run the following command:

1
2

# Download the absolute latest commit
$ composer create-project symfony/skeleton my_project -s dev

Once the command finishes, you’ll have a new Symfony project created in the my_project/ directory.

Upgrading your Project to an Unstable Symfony Version¶

Suppose again that Symfony 4.0 hasn’t been released yet and you want to upgrade an existing application to test that your project works with it.

First, open the composer.json file located in the root directory of your project. Then, edit the value of all of the symfony/* libraries to the new version and change your minimum-stability to beta:

1
2
3
4
5
6
7
8

{
    "require": {
+         "symfony/framework-bundle": "^4.0",
+         "symfony/finder": "^4.0",
        "...": "..."
    },
+     "minimum-stability": "beta"
}

You can also use set minimum-stability to dev, or omit this line entirely, and opt into your stability on each package by using constraints like 4.0.*@beta.

Finally, from a terminal, update your project’s dependencies:

1

$ composer update

After upgrading the Symfony version, read the Symfony Upgrading Guide to learn how you should proceed to update your application’s code in case the new Symfony version has deprecated some of its features.

1
2
3
4
5
6
7
8

$ cd projects/my_project/
$ git checkout -b testing_new_symfony
# ... update composer.json configuration
$ composer update "symfony/*"

# ... after testing the new Symfony version
$ git checkout master
$ git branch -D testing_new_symfony