Symfony Blog

This week Symfony entered into the "feature freeze" period for the upcoming 3.3 version. This means that the development activity will slow down to focus on stabilizing the new features introduced in Symfony 3.3. Meanwhile, the SymfonyLive Paris 2017 conference took place this week with great success.

Symfony 3.3 adds a new command called "about" to display useful information about your Symfony application and your PHP environment.

Symfony 3.3 adds a new versioning strategy based on JSON file manifests, which is used by popular tools such as Webpack.

Symfony 3.3 deprecates the ConsoleEvents::EXCEPTION event in favor of a new ConsoleEvents::ERROR event that is able to handle also the exceptions thrown from listeners.

The symfony.com website contents will no longer be available in languages different than English.

Symfony 3.3 adds a new Lock component that supports different stores (flock, semaphore, Redis, Memcache), auto-expiring locks and combining multiple lock stores.

This week, Symfony introduced a new Lock component, added explicit service locators, improved the performance of the route matching,introduced a new AbstractController to replace ControllerTrait, reverted getter injection and continued improving autowiring.

Symfony 3.3 adds full support for loading config files using glob patterns, both for the container and the routing file loaders.

Symfony 3.3 deprecates the warmup part of the cache:clear because it does not work well and it doesn't guarantee that the generated cache is exactly the same as the one that would have been generated via cache:warmup.

Symfony 3.3 adds new features to simplify services configuration thanks to the default config options and the interface-based config options.