Play 2.6.0-M2, 2.5.13 and 2.4.11 released!
Marcos Pereira
Hi all,
The Play team is proud to announce the second milestone of Play 2.6.0. Like the previous milestone, the main goal is to get feedback, so please let us know if something isn't working or you see something that should be improved.
Please note that this is intended to be a preview of the 2.6.0 release and we would not recommend using this release in a production application. We have made an effort to introduce most major API changes in this release, but we reserve the right to break everything in a future milestone or release candidate.
We are also releasing Play 2.5.13 and 2.4.11, with bug fixes and some improvements.
Finally, we are trying a new release process. From now on we will do a time-based release train approach. We still have to nail some details, but our idea is to have the following time slices:
Play 2.6 Milestones: every two weeks until we get a final/stable release
Current stable (2.5.x): every month (if there are any changes), or for bug and security fixes at Play team's discretion
Old stable (2.4.x): every two months (if there are any changes) and for security patches at Play team's discretion
Of course, for the current and old stable releases, we only release compatible version (there are breaking changes only if they are extremely necessary).
So, this is our first release train:
Play 2.6.0-M2
We had great contributions (feedback, pull requests, issues, etc) from the community. Improvements were made to the migration guide, compile time dependency injection and new APIs were added. You can see the list of changes here:
https://github.com/playframework/playframework/releases/tag/2.6.0-M2
One of the main changes in this releases is that now Play has a default set of filters:
https://github.com/playframework/playframework/pull/7023
We added extensive documentation in our Migration Guide about how to adapt your application and tests. The intention is to give your application better security out of the box, and if don't need it, you can easily turn it off or configure according your needs.
Play 2.5.13
Play 2.5.13 has a number of bug fixes and also documentation improvements. One of the changes is that we added a note about Lucidchart migration from Play 2.3 to Play 2.5. This is an amazing write up about their experience. Take a look at it if you didn't yet:
https://www.lucidchart.com/techblog/2017/02/22/upgrading-play-framework-2-3-play-2-5/
You can see all the changes here:
https://github.com/playframework/playframework/milestone/49?closed=1
Play 2.4.11
Play 2.4.11 is a bug fixes release. You can see the changes here:
https://github.com/playframework/playframework/milestone/51?closed=1
Standalone modules
We are also releasing new milestone versions of our standalone modules:
play-json 2.6.0-M5
This release adds more features and some new Codecs to play-json:
play-ebean 4.0.0-M2
Now with support to an updated version of Ebean (10.1.6).
play-slick:
We are releasing two version of play-slick:
2.1.0 Final:
This version is compatible with Play 2.5.x and Slick 3.2.0
3.0.0-M3
This version is compatible with Play 2.6.x and Slick 3.2.0
scalatestplus-play
We are also releasing two versions of scalatestplus-play:
2.0.0 Final
This version is compatible with Play 2.5.x and Scalatest 3.0.1.
3.0.0-M1
This version is compatible with Play 2.6.x and Scalatest 3.0.1. The list of changes:
We had previously released 2.0.0-M2 version compatible with Play 2.6.x, but this was just a small glitch during our release process. To made it clear which version of scalatestplus-play is compatible with Play, please, see the the table here:
https://github.com/playframework/scalatestplus-play#releases
Feel free to send us feedback about the releases and also about the new release process.
William Narmontas
James Ward
It looks like that header was removed at sometime in the past but regressed back in.