Proposal: Upgrade CI to Java 17
Problem
GitHub Actions CI builds are currently failing with the following error:
Required Java version 17 is not met by current version: 11.0.30
Root Cause
The quarkus-maven-plugin:3.6.9 (inherited from service-parent:5) requires Java 17 minimum:
<requiredJavaVersion>17</requiredJavaVersion>
<requiredMavenVersion>3.9.6</requiredMavenVersion>
GitHub Actions runner environments were recently upgraded from Maven 3.8.x to Maven 3.9.6+. Maven 3.9.6+ strictly enforces plugin prerequisites, causing all PR builds to fail since March 16, 2026.
Timeline:
Proposal: Upgrade to Java 17
We should upgrade our CI environment and runtime to Java 17 for the following reasons:
- Quarkus 3.x officially requires Java 17+ - We're already using Quarkus 3.6.9
- Java 11 LTS support ends September 2026 - Only 6 months away
- Maven ecosystem moving forward - Maven 3.9.6+ enforces Java 17 for Quarkus plugins
- Aligns with industry standards - Java 17 is the current LTS baseline
Required Changes
CI Workflows
.github/workflows/pr-build.yml: Update java-version: '17'
.github/workflows/merge-build.yml: Update java-version: 17
Runtime Environment
- Update Dockerfiles to use Java 17 base images
- Update Kubernetes/OpenShift deployment manifests
- Validate all dependent services are compatible with Java 17
Testing
- Run integration tests with Java 17
- Validate all services in the ecosystem
Impact
Currently blocked:
Why local builds still work:
- Local Maven 3.8.8 doesn't strictly enforce plugin prerequisites
- CI uses Maven 3.9.6+ which enforces them
References
Proposal: Upgrade CI to Java 17
Problem
GitHub Actions CI builds are currently failing with the following error:
Root Cause
The
quarkus-maven-plugin:3.6.9(inherited fromservice-parent:5) requires Java 17 minimum:GitHub Actions runner environments were recently upgraded from Maven 3.8.x to Maven 3.9.6+. Maven 3.9.6+ strictly enforces plugin prerequisites, causing all PR builds to fail since March 16, 2026.
Timeline:
ubuntu-latestrunner upgraded Maven to 3.9.6+Proposal: Upgrade to Java 17
We should upgrade our CI environment and runtime to Java 17 for the following reasons:
Required Changes
CI Workflows
.github/workflows/pr-build.yml: Updatejava-version: '17'.github/workflows/merge-build.yml: Updatejava-version: 17Runtime Environment
Testing
Impact
Currently blocked:
Why local builds still work:
References