0.5.0 — Play 2.8 and 2.9 support

Play 2.8 and 2.9 applications can now add WebMCP without migrating to Play 3. Java and Scala sites use the same Twirl helpers and browser runtime, with a separate artifact for each Play line.

Play version	Dependency artifact	Scala	Java
3.0.0–3.0.11	play-webmcp	2.13, 3	11, 17, 21
2.9.0–2.9.11	play-webmcp-play29	2.13, 3	11, 17, 21
2.8.0–2.8.22	play-webmcp-play28	2.12, 2.13	8, 11

All artifacts use version 0.5.0 and group io.github.alexusel. Choose exactly one artifact for your Play line. Keep your existing compatible Play, Scala, and sbt setup. Installation checks verify that adding the module preserves the application's Play, Scala, Twirl, JSON, and Akka/Pekko dependencies.

The Play 2.8 variants are built against Play 2.8.0 with Java 8 bytecode. The Play 2.9 and Play 3 variants use Java 11 bytecode. The public asset paths stay lib/play-webmcp/play-webmcp.js and lib/play-webmcp/play-webmcp.global.js for all variants.

Validation includes all listed Play patch releases, minimum Scala versions and older sbt builds, Java and Scala applications, and native Chromium scenarios at / and /shop. The tests cover ordinary forms, CSRF, tool calls, component cleanup, cancellation, and failed requests. CI run.

See the English README for dependency lines, prerequisites, examples, and the exact test matrix. Upgrading an existing installation requires cleaning the extracted WebJar assets before rebuilding.

This is an experimental WebMCP release. Browser and agent support is separate from Play compatibility. Play 2.0–2.7 and Play 1.x are outside this release's JVM compatibility range.

Assets include binary, source, and documentation JARs plus POMs for all six variants; the two standalone browser runtimes; and SHA256SUMS. The same artifacts are distributed through the repository's public Maven branch.