Update dependency org.playframework:sbt-plugin to v3.0.11 - #5
Open
renovate[bot] wants to merge 1 commit into
Open
Update dependency org.playframework:sbt-plugin to v3.0.11#5renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/org.playframework-sbt-plugin-3.x
branch
from
June 30, 2025 23:43
d59545c to
e5993fe
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/org.playframework-sbt-plugin-3.x
branch
from
September 11, 2025 13:47
e5993fe to
462613f
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/org.playframework-sbt-plugin-3.x
branch
from
December 22, 2025 02:35
462613f to
4856750
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/org.playframework-sbt-plugin-3.x
branch
from
May 21, 2026 07:48
4856750 to
69db8e7
Compare
renovate
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.6→3.0.11Release Notes
playframework/playframework (org.playframework:sbt-plugin)
v3.0.11: Play 3.0.11Compare Source
The Play Team is delighted to announce the release of Play 3.0.11! 🎉
📗 About this Release
This release fixes several bugs and addresses reported security vulnerabilities (CVEs) in play-ws and - as always - updates dependencies. We strongly recommend upgrading at your earliest convenience.
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
pekko.http.server.enable-http2(backport #13750) by @pjfanningFollowing pull requests got merged for this release:
@deprecated/@sinceby @mkurzpekko.http.server.enable-http2(backport #13750) by @pjfanningFor more details see the full list of changes and the 3.0.11 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)!
v3.0.10: Play 3.0.10Compare Source
We are pleased to announce the release of Play 3.0.10! 🎉
📗 About this Release
This release fixes several bugs and addresses reported security vulnerabilities (CVEs) and - as always - updates dependencies. We strongly recommend upgrading at your earliest convenience.
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
We now limit the maximum allowed nesting depth of JSON structures (arrays, objects, or a mix of both) to 1000.
This limit can be adjusted using the system property
play.json.parser.maxNestingDepth.We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
This change helps prevent both potential
OutOfMemoryErrors andStackOverflowErrors.The latter, however, is not a concern for Play JSON, since it already uses a @tailrec-optimized parsing method.
As a result, Play JSON is not affected by GHSA-h46c-h94j-95f3, which specifically addresses StackOverflowError risks.
This improvement is simply an additional safety measure.
ch.qos.logback:logback-coreto fix CVE-2025-11226 (see "Patch updates" below)Following pull requests got merged for this release:
For more details see the full list of changes and the 3.0.10 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)!
v3.0.9: Play 3.0.9Compare Source
The Play Team is happy to announce the release of Play 3.0.9! 🎉
📗 About this Release
This patch release upgrades dependencies, fixes minor bugs, comes with support for Java 25 and improves compatibility with Scala 3. 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.
Official support for Java 25
Starting with this release, Play officially supports Java 25. Since all tests passed when running on the latest Java 25 release candidate, we are comfortable declaring Java 25 officially supported by Play.
Noteworthy Pull Requests
onClientErrorfrom the server backend was missing theHttpErrorInfoattr (backport #13416) by @mkurzFull Changelog
Following pull requests got merged for this release:
onClientErrorfrom the server backend was missing theHttpErrorInfoattr (backport #13416) by @mkurzFor more details see the full list of changes and the 3.0.9 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)!
v3.0.8: Play 3.0.8Compare Source
The Play Team is happy to announce the release of Play 3.0.8! 🥳
📗 About this Release
This release fixes several bugs and a CVE, improves Scala 3 support, and - as always - updates dependencies. We strongly recommend upgrading at your earliest convenience.
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.
sbt 1.9.0 or newer is now required
Because of recent changes in how artifacts are published to Maven Central, older sbt versions can no longer retrieve Play's sbt plugins published starting July 1, 2025. If you're still using an older sbt release, you'll need to upgrade to sbt 1.9.0 or newer to continue fetching Play artifacts from Maven Central. Play 3.0.8 and newer will not work with earlier sbt versions. To be fair, when releasing Play 3.0, we already announced 1.9.0 as the minimum required sbt version, even though older versions may still have worked until now.
Scala 3 improvements
Twirl now supports
usingin it's templates, so you can define template parameters like:Thanks to @ajafri2001 for implementing this improvement 🙌:
playframework/twirl#933 Prepend "using" at the callsite when definition site has implicit parameter
When using Play JSON, the JSON field ordering is now correctly preserved when compiling with Scala 3 - implemented by @xuwei-k:
playframework/play-json#1177 fix field ordering Scala 3 writes macro
Noteworthy Pull Requests
ClassCastExceptionwhen using@WithJava annotation by @mkurzFull Changelog
Following pull requests got merged for this release:
ClassCastExceptionwhen using@WithJava annotation by @mkurzFor more details see the full list of changes and the 3.0.8 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)!
v3.0.7: Play 3.0.7Compare Source
The Play Team is happy to announce the release of Play 3.0.7.
📗 About this Release
This patch release primarily upgrades dependencies, fixes minor bugs, and improves compatibility with Scala 3. 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
RoutingDsl.{Route,RouteParam}(backport #13003) by @WojciechMazurFull Changelog
Following pull requests got merged for this release:
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.