2.7.3

• harden the JsonToFormDecoder to not error on non-array input (#2145)

2.7.2

• fixed serializing Error instances when the Symfony Serializer is used (#2110)
• fixed serializing Error instances when JMS Serializer is used (#2105)
• fixed compatibility with null owner returned by SensioFrameworkExtraBundle (#2097)
• completely fixed handling Throwable objects in ExceptionController::showAction(), continues #2093 (#2096)

2.7.1

• fixed handling all Throwable objects in ExceptionController::showAction() (#2093)
• fixed ViewHandlerInterface alias definition (#2085)

2.7.0

• ignore SessionInterface and UserInterface controller action arguments
• fixed ExceptionListener deprecation warning
• fixed ControllerNameParser deprecation warning
• fixed DisableCSRFExtension::getExtendedTypes() return type
• improved EngineInterface error message in ViewHandler
• improved Symfony 4.4 compatibility
• automatically use Twig as templating engine when available

2.6.0

• ensure compatibility with the FlattenException from the new ErrorRenderer component
• fix handling the serialize_null option with the Symfony serializer
• added support for using multiple constraints for the requirements option of the @RequestParam
  annotation
• drop support for PHP 5.5, 5.6 and 7.0
• drop support for SF 4.0, 4.1 and 4.2 (3.4 LTS is still supported)
• deprecated using the ParamFetcher class without passing a validator as the third argument, this
  argument will become mandatory in 3.0
• fix compatiblity without the deprecated templating in Symfony 4.3; see #2012 on how to configure the FOSRestBundle
• removed symfony/templating from the dependencies; if you still use it you need to require it in your app

2.5.0

• compatibility with Symfony 4.2
• deprecated the FOSRestController base class, use the new AbstractFOSRestController instead
• dropped support for Symfony 2.7 to 3.3
• compatibility with JMS Serializer 2 and JMSSerializerBundle 3
• overwrite rules when they are defined in different config files instead of throwing exceptions
• fixed using the nullable option of the param annotations when the map option is enabled
• ensure a predictable order of routes by sorting controllers by name when loading classes from a directory
• reset the internal state of the view handler to fix compatibility with PHP-PM
• fix different bugs related to the handling of API versions (see #1491, #1529, #1691)

2.4.0: fix route generator not ignoring body param converters (#1934)

[BC break] @Route::$service is no longer supported, see the changelog and #1822.

This release primarily fixes deprecations.

2.3.1

• improved Symfony 4 compatibility

• manually decorate the core JMS handler registry

• run checks after SensioFrameworkExtraBundle

• made the view handler alias public

• check for definitions before they might be removed

• added Yaml routing resource support

• refactored several unit tests

2.3.0

• added support for file paths to the directory route loader

• added support for context factories when using JMS Serializer

• the RequestBodyParamConverter ignores unrelated controller arguments to not conflict with Symfony's built-in
  argument resolver

• made the bundle compatible with SensioFrameworkExtraBundle 4.x

• added some interface aliases to support by ID autowiring

• added support for custom keys for groups when using JMSSerializerBundle

• allow to load FOSRestBundle inside the kernel before JMSSerializerBundle

• added the fos_rest.routing_loader.prefix_methods option to disable method name prefixes in generated route names

• removed newline characters from exception messages

2.2.0: typo in UPGRADING-2.0.md fixed (#1690)

* typo in UPGRADING-2.0.md fixed

* Update UPGRADING-2.0.md