Sunbird v8.1.0 (Latest)

Release notes for Sunbird Release 8.1.0 - 16th December 2025

This release focuses on platform modernization, framework upgrades, and service consolidation, ensuring better maintainability, improved performance, and long-term support readiness. Major backend components have been upgraded to supported versions, and architectural changes have been introduced to streamline services.

Jira Tickets for Release 8.1.0: https://project-sunbird.atlassian.net/issues?filter=13113

Key Highlights of the Release

  1. Backend Framework Modernization

    a. Migration from Akka to Pekko

    • Replaced Akka 2.5.22 with Pekko 1.0.3 across backend services.

    • Removes dependency on Akka’s business source license.

    • Ensures long-term sustainability by adopting a fully open-source alternative.

    b. Play Framework Upgrade

    • Upgraded Play Framework 2.4.x/2.7.x/2.8.x (EOL) to Play 3.0.5.

    • Improves performance, security, and compatibility with modern tooling.

    • Enables better support for newer Java and Scala versions.

    c. Scala Version Upgrade

    • Upgraded Scala from Scala 2.11.x/2.12.x to Scala 2.13.12.

  2. Frontend Enhancements

    Portal Angular Upgrade

    • Upgraded Angular from v14 to v16 for improved performance and maintainability.

  3. Architecture & Service Changes

    Deprecation of Learning Service

    • The Learning Service has been officially deprecated.

    • All Assessment-related APIs have been moved to the Inquiry: Assessment Service.

    • Modernizes the codebase by removing deprecated APIs.

  4. Node.js Runtime Upgrade (Middleware Services)

    Upgraded Node.js from version 12 to 22.17.1 (LTS) for the following services:

    • knowlg-mw-service

    • discussion-middleware

    This change addresses known security vulnerabilities, improves runtime performance, and ensures continued support with an actively maintained Node.js version.

Discussion Forum Configuration Guide

Refer to the Sunbird Discussion Forum Configuration Guide for step-by-step instructions on:

Migration Guide

  1. Load the appropriate env.json file containing the required environment variables.

  2. Run the following APIs in Postman:

    • Forms -> Content: 5 - Book Create API

    • Forms -> Ed: 1 - Menubar form - Creation for all rootOrg API

    • Forms -> Ed: 13 - Resource Create API

    • Forms -> Ed: 17 - Questionset API

Last updated