Skip to content

java 17+ compatibility upgrade#2

Open
balaji-pc wants to merge 1 commit intomasterfrom
update/java-17-compatability
Open

java 17+ compatibility upgrade#2
balaji-pc wants to merge 1 commit intomasterfrom
update/java-17-compatability

Conversation

@balaji-pc
Copy link

@balaji-pc balaji-pc commented Dec 8, 2025

Overview

  • This release modernizes the project to support Java 17+ and updates all dependencies to their latest compatible versions.
  • This ensures the library continues to work with modern Java environments and benefits from recent security updates and improvements.

Breaking Changes

Important: This is a breaking release. Users will need to upgrade their environment:

  • Java 17 or higher is now required (previously Java 8-11)
  • Scala 2.13 only - Scala 2.12 support has been dropped
  • Users on older Java versions should continue using version 0.9.x

📋 Version Compatibility

Version Java Scala Status
0.10.0+ 17+ 2.13 ✅ Current release
0.9.x 8-11 2.12, 2.13 Legacy (for older environments)

Testing

  • Test suite verified on Java 17
  • 1064 tests executed successfully

Migration Guide

For users upgrading from 0.9.x:

  1. Upgrade to Java 17 or higher
  2. Update Scala to 2.13.16 (if using Scala 2.12)
  3. Update dependency version to 0.10.0

No code changes required - the API remains unchanged.

@balaji-pc balaji-pc added enhancement New feature or request good first issue Good for newcomers dependencies Infrastructure and dependencies update and removed enhancement New feature or request labels Dec 8, 2025
Copy link

@themetaschemer themetaschemer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I can't check whether each of these changes are good or not. I'm assuming it has been properly tested. However, before you merge this, you should set up a confluence document about the upgrade process. What each developer needs to do and how to make sure everything is working properly in the dev environment. Also, you should probably roll this out one developer at a time because I don't want the whole team to be stuck at the same time if we merge this branch. Please work with @shivab518 to develop a rollout plan.

@themetaschemer
Copy link

@copilot please review.

Copy link

Copilot AI commented Jan 6, 2026

@themetaschemer I've opened a new pull request, #3, to work on those changes. Once the pull request is ready, I'll request review from you.

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

Labels

dependencies Infrastructure and dependencies update good first issue Good for newcomers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants