Skip to content

Releases: playframework/playframework

Play 3.0.4

17 Jun 15:43
@github-actions github-actions
3.0.4
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
fafc043
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 3.0.4 Latest
Latest

The Play Team is delighted to announce the release of Play 3.0.4! 🎉

📗 About this Release

This patch release addresses a couple of bugs and upgrades dependencies. We recommend upgrading as soon as possible.

If you're considering upgrading to Play 3.0, please check the Play 3.0 release announcement for highlights and further details on how to migrate. Many projects have already smoothly upgraded to Play 3.0.

Noteworthy Pull Request

  • #12724 [3.0.x] Update changed assets in subprojects (backport #12721) by @mkurz
    • Fixes #12484 "Asset changes in subprojects" by @n4cer
    • Fixes #12636 "Issue with sbt-web/sassify, sub-projects, and the Play dev server..." by @mikesname

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 3.0.4 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

jilen, mkurz, and 6 other contributors
Assets 2
Loading
0 Join discussion

Play 2.9.4

17 Jun 15:43
@github-actions github-actions
2.9.4
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
3c8156e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.9.4

The Play Team is delighted to announce the release of Play 2.9.4! 🎉

📗 About this Release

This patch release addresses a couple of bugs and incompatibilities, and upgrades dependencies. We recommend upgrading as soon as possible.

If you're considering upgrading to Play 2.9, please check the Play 2.9 release announcement for highlights and further details on how to migrate. Many projects have already smoothly upgraded to Play 2.9.

Noteworthy Pull Requests

  • #12719 [2.9.x] Fix https compatibility with akka-http 10.6.x by @dwickern
    • Fixes #12711 "Play 2.9 incompatible with akka-http 10.6.x when using https" by @dwickern
  • #12725 [2.9.x] Update changed assets in subprojects (backport #12721) by @mkurz
    • Fixes #12484 "Asset changes in subprojects" by @n4cer
    • Fixes #12636 "Issue with sbt-web/sassify, sub-projects, and the Play dev server..." by @mikesname

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 2.9.4 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

jilen, mkurz, and 6 other contributors
Assets 2
Loading
0 Join discussion

Play 2.8.22 (End of life)

05 Jun 06:38
@github-actions github-actions
2.8.22
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
4564a5c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.8.22 (End of life)

🚨 This is the last Play 2.8 release!

Caution

From now on, you will no longer receive security updates for your Play 2.8 applications!

We recommend upgrading to Play 2.9 (built on Akka) or Play 3.0 (built on Pekko) as soon as possible:

More details on EOL (end of life) dates and how Play deals with Akka’s License change can be found here.

📗 Following pull requests got merged for this last Play 2.8 release:

For more details see the full list of changes and the 2.8.22 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

wsargent, mkurz, and scala-steward
Assets 2
Loading
0 Join discussion

Play 3.0.3

07 May 09:46
@github-actions github-actions
3.0.3
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
dd4a674
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 3.0.3

The Play Team is happy to announce the release of Play 3.0.3! 🥳

📗 About this Release

This patch release addresses a couple of bugs, improves support for Scala 3, and upgrades dependencies. We recommend upgrading as soon as possible.

If you're considering upgrading to Play 3.0, please check the Play 3.0 release announcement for highlights and further details on how to migrate. Many projects have already smoothly upgraded to Play 3.0.

Noteworthy Pull Requests

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 3.0.3 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

mkurz, ihostage, and 3 other contributors
Assets 2
Loading
0 Join discussion

Play 2.9.3

07 May 09:46
@github-actions github-actions
2.9.3
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
ae8abc0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.9.3

The Play Team is happy to announce the release of Play 2.9.3! 🥳

📗 About this Release

This patch release addresses a couple of bugs, improves support for Scala 3, and upgrades dependencies. We recommend upgrading as soon as possible.

If you're considering upgrading to Play 2.9, please check the Play 2.9 release announcement for highlights and further details on how to migrate. Many projects have already smoothly upgraded to Play 2.9.

Noteworthy Pull Requests

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 2.9.3 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

mkurz, ihostage, and 3 other contributors
Assets 2
Loading
0 Join discussion

Play 3.0.2

01 Mar 16:26
@github-actions github-actions
3.0.2
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
3a56c2a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 3.0.2

The Play Team is pleased to announce the release of Play 3.0.2! 🎉

📗 About this Release

This patch release addresses several bugs and introduces minor enhancements that may benefit you. We strongly recommend upgrading at your earliest convenience.

If you're considering upgrading to Play 3, please check the Play 3 release announcement for highlights and further details on how to migrate.

Noteworthy Pull Requests

  • With this release, we are disabling HTTP pipelining in the Play Pekko HTTP backend. HTTP pipelining has not been thoroughly tested within Pekko HTTP and was already disabled in Pekko HTTP itself some time ago. Beyond benchmarking purposes, it is not recommended for practical use, and there is minimal actual usage from common client libraries in their default settings (web browsers do not support it anymore). Furthermore, having HTTP pipelining enabled could lead to Play unexpectedly canceling POST requests with large bodies.
    • #12397 Disable HTTP pipelining by @mkurz
    • #12351 Requests with Large POST Body Immediately Goes into Delay Cancellation Right After the Server Received the Request by @raphaelNguyen
  • Resolved an issue that could result in the loss of result attributes:
  • Netty native transports under Linux (enabled with play.server.netty.transport = "native") now support AArch64 and RISC-V out of the box in Play:
    • #12405 Make Netty native transport work on Linux AArch64 and RISC-V (besides x86-64) by @mkurz
  • Play and Twirl are now compatible with Scala 3.4.0. However, it's important to note that Scala 3.4.0 is not a Long-Term Support (LTS) release, and Play officially supports only Scala LTS versions (currently Scala 3.3). This compatibility is provided as a best effort. Consequently, if you choose to upgrade beyond Scala 3.3, you do so at your own risk, and you should not expect support for issues that may arise.
  • If you are using Bower WebJars you will now see deprecation warnings. More details:
  • You now have the option to disable the generation of JavaScript (reverse) routers if you do not utilize them, potentially enhancing the performance of your build:
  • This release includes numerous dependency upgrades, notably:
  • Last but not least, over the past weeks (indeed, months), efforts have been made to transition Play and all its dependencies away from the deprecated (and read-only) repo.typesafe.com and repo.scala-sbt.org repositories. As a result, with this release, all dependencies (including those for testing) are now hosted exclusively on Maven Central. This change ensures that even if one of the deprecated repositories were to become unavailable (as has happened in the past), your projects would not be affected. Moreover, this move allows for the possibility that, 15 years from now, you could still download the Play 3.0.2+ source code and, with just Java and sbt installed, rebuild Play from the sources (assuming Maven Central is still operational, which is more likely). While this may seem a bit far-fetched, we occasionally receive reports from users attempting to rebuild an ancient Play release but are unable to do so because they cannot retrieve all the necessary dependencies.

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 3.0.2 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

jamesward, reardonj, and 11 other contributors
Assets 2
Loading
1 Join discussion

Play 2.9.2

01 Mar 16:26
@github-actions github-actions
2.9.2
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
1f9875a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.9.2

The Play Team is pleased to announce the release of Play 2.9.2! 🎉

📗 About this Release

This patch release addresses several bugs and introduces minor enhancements that may benefit you. We strongly recommend upgrading at your earliest convenience.

If you're considering upgrading to Play 2.9, please check the Play 2.9 release announcement for highlights and further details on how to migrate.

Noteworthy Pull Requests

  • With this release, we are disabling HTTP pipelining in the Play Akka HTTP backend. HTTP pipelining has not been thoroughly tested within Akka HTTP and was already disabled in Akka HTTP itself some time ago. Beyond benchmarking purposes, it is not recommended for practical use, and there is minimal actual usage from common client libraries in their default settings (web browsers do not support it anymore). Furthermore, having HTTP pipelining enabled could lead to Play unexpectedly canceling POST requests with large bodies.
    • #12397 Disable HTTP pipelining by @mkurz
    • #12351 Requests with Large POST Body Immediately Goes into Delay Cancellation Right After the Server Received the Request by @raphaelNguyen
  • Resolved an issue that could result in the loss of result attributes:
  • Netty native transports under Linux (enabled with play.server.netty.transport = "native") now support AArch64 and RISC-V out of the box in Play:
    • #12405 Make Netty native transport work on Linux AArch64 and RISC-V (besides x86-64) by @mkurz
  • Play and Twirl are now compatible with Scala 3.4.0. However, it's important to note that Scala 3.4.0 is not a Long-Term Support (LTS) release, and Play officially supports only Scala LTS versions (currently Scala 3.3). This compatibility is provided as a best effort. Consequently, if you choose to upgrade beyond Scala 3.3, you do so at your own risk, and you should not expect support for issues that may arise.
  • If you are using Bower WebJars you will now see deprecation warnings. More details:
  • You now have the option to disable the generation of JavaScript (reverse) routers if you do not utilize them, potentially enhancing the performance of your build:
  • This release includes numerous dependency upgrades, notably:
  • Last but not least, over the past weeks (indeed, months), efforts have been made to transition Play and all its dependencies away from the deprecated (and read-only) repo.typesafe.com and repo.scala-sbt.org repositories. As a result, with this release, all dependencies (including those for testing) are now hosted exclusively on Maven Central. This change ensures that even if one of the deprecated repositories were to become unavailable (as has happened in the past), your projects would not be affected. Moreover, this move allows for the possibility that, 15 years from now, you could still download the Play 2.9.2+ source code and, with just Java and sbt installed, rebuild Play from the sources (assuming Maven Central is still operational, which is more likely). While this may seem a bit far-fetched, we occasionally receive reports from users attempting to rebuild an ancient Play release but are unable to do so because they cannot retrieve all the necessary dependencies.

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 2.9.2 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

jamesward, reardonj, and 10 other contributors
Assets 2
Loading
0 Join discussion

Play 3.0.1

10 Jan 10:07
@github-actions github-actions
3.0.1
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
0a4a153
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 3.0.1

The Play Team is delighted to announce the release of Play 3.0.1! 🥳

📗 About this Release

This is a pure patch release, not shipping any new features, but upgrading dependencies and fixing minor bugs reported by the community since our major Play 3 release two months ago. Many projects have already smoothly upgraded to Play 3.

If you're considering upgrading to Play 3, please check the Play 3 release announcement for highlights and further details on how to migrate.

Noteworthy Pull Requests

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 3.0.1 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

inigo, jamesward, and 8 other contributors
Assets 2
Loading
0 Join discussion

Play 2.9.1

10 Jan 10:07
@github-actions github-actions
2.9.1
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
34c8cd4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.9.1

The Play Team is delighted to announce the release of Play 2.9.1! 🥳

📗 About this Release

This is a pure patch release, not shipping any new features, but upgrading dependencies and fixing minor bugs reported by the community since our major Play 2.9 release two months ago. Many projects have already smoothly upgraded to Play 2.9.

If you're considering upgrading to Play 2.9, please check the Play 2.9 release announcement for highlights and further details on how to migrate.

Noteworthy Pull Requests

Full Changelog

Following pull requests got merged for this release:

For more details see the full list of changes and the 2.9.1 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

inigo, jamesward, and 7 other contributors
Assets 2
Loading
0 Join discussion

Play 2.8.21

09 Nov 13:49
@github-actions github-actions
2.8.21
This tag was signed with the committer’s verified signature.
mkurz Matthias Kurz
GPG key ID: 0B4AAA92F1117EF5
Learn about vigilant mode.
2c3c424
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Play 2.8.21

The Play Team is happy to announce the release of Play 2.8.21 🥳

⚠️ Play 2.8 will reach its end of life on May 31st, 2024

More details on EOL dates, supported dependencies and how Play deals with Akka’s License change can be found here.
We recommend upgrading to Play 2.9 (built on Akka) or Play 3.0 (built on Pekko) as soon as possible:

📗 Noteworthy in this release

  • #11915 [2.8.x] Fix missed ContextInitializer#configureByResource (backport #11910) by @tsuyoshizawa
    Logback 1.4.9 and 1.3.9 broke their public APIs so we had to introduce a workaround so you can upgrade to those versions.
  • #12186 [2.8.x] Better Scala 2.13.12 compatibility by @mkurz
    If you want to use Scala 2.13.12 in your projects, this change should avoid some warnings and maybe even errors, depending on your configured compiler flags.
  • #12046 [2.8.x] Netty 4.1.100 by @mkurz
    We upgraded Netty to benefit from latest security fixes.

Besides that, following pull requests got merged for this release:

For more details see the full list of changes and the 2.8.21 milestone.

❤️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

🙇 Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!

Contributors

xuwei-k, mkurz, and 3 other contributors
Assets 2
Loading
0 Join discussion