Skip to content

Conversation

@sntiwari1
Copy link

@sntiwari1 sntiwari1 commented Oct 9, 2025

Pull Request Summary

This PR upgrades the project from Play Framework 2.7.2 + Akka 2.5.22 + Scala 2.12.11 to Play Framework 3.0.5 + Apache Pekko 1.0.2 + Scala 2.13.12.

The upgrade ensures the project uses actively maintained, secure, and license-compliant dependencies. It also updates Scala collection APIs, test frameworks, and logging libraries for compatibility with the new versions.

Issue Fixed: N/A (general upgrade and maintenance)

Motivation and Context:

  • End-of-life software (Play 2.7.2, Akka 2.5.22)
  • License compliance (Akka → commercial license; Pekko → Apache License 2.0)
  • Security updates and performance improvements (Scala 2.13, Play 3.0)
  • Modern features and better test framework support

Dependencies:

  • Scala 2.13.12
  • Apache Pekko 1.0.2
  • SLF4J 2.0.9
  • Logback 1.4.14
  • Jackson 2.14.3
  • Guice 5.1.0

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature / Upgrade (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Ran full project build with mvn clean install -DskipTests
  • Ran distribution packaging (mvn play2:dist) and application startup
  • Verified Akka → Pekko migration and Scala 2.13 API changes in unit tests

Test Configuration:

  • Software versions: Java 11, Play 3.0.5, Scala 2.13.12, Pekko 1.0.2, Redis 5.0.3
  • Hardware versions: 2 CPU / 4GB RAM

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Files Modified / Key Changes

  • Maven POMs: Updated dependencies for Play 3.0.5, Scala 2.13.12, Pekko 1.0.2
  • Java/Scala files: All Akka imports updated to Pekko; Scala 2.13 collection APIs adjusted
  • Configuration files: application.conf updated from akkapekko

Description by Korbit AI

What change is being made?

Upgrade the entire Play/Scala/Akka stack from Play 2.7.x with Akka 2.5.x and Scala 2.12 to Play 3.0.5 + Apache Pekko 1.0.x + Scala 2.13, updating code imports, configuration, tests, and Maven/Gradle dependencies across modules to migrate from Akka to Pekko and align with the new ecosystem.

Why are these changes being made?

These changes address end-of-life software and licensing concerns, replacing Akka with Pekko under an Apache-compatible license, while adopting Scala 2.13 and Play 3 features for improved security, performance, and modern APIs. The migration also updates test and build configurations to reflect the new dependencies and API changes.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copilot AI and others added 25 commits October 7, 2025 12:54
Updated Java and Scala dependencies, improved build instructions, and clarified migration details.
Removed commented dependency for Netty native resolver on Mac Apple Silicon.
Updated UPGRADE_PLAY.md to reflect changes in upgrade instructions and added a note about play.server.netty.transport configuration.
Upgrade to Scala 2.13.12 + Play Framework 3.0.5 + Apache Pekko 1.0.2
@korbit-ai
Copy link

korbit-ai bot commented Oct 9, 2025

Based on your review schedule, I'll hold off on reviewing this PR until it's marked as ready for review. If you'd like me to take a look now, comment /korbit-review.

Your admin can change your review schedule in the Korbit Console

@sntiwari1 sntiwari1 changed the base branch from release-8.0.0 to release-8.1.0 October 9, 2025 09:39
Copilot AI and others added 2 commits October 17, 2025 11:21
… to fail after deployment

Fix logging configuration - remove invalid nested layout causing logs to fail after deployment
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant