Skip to content

Move to Java 25 and Spring Boot 3.5, fix CI - #1

Merged
marlware merged 10 commits into
mainfrom
upgrade-java-25
Oct 13, 2026
Merged

marlware merged 10 commits into
mainfrom
upgrade-java-25

Conversation

@marlware

@marlware marlware commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Moves the project from Java 21 to Java 25 and bumps Spring Boot from 3.3.4 to 3.5.16 (Spring Cloud to 2025.0.3). I stayed on 3.5 and not 4.x because 4 looked like a bigger job, can do that later.

Also fixed the GitHub Actions pipeline, and threw in a few small cleanups.

Upgrade

  • Boot and Spring Cloud versions in the parent pom
  • Java 25 in the pom, the Dockerfiles and the README
  • Took out the Byte Buddy experimental flag, tests are fine without it now

CI

  • It was still on JDK 21, which can't build this anymore
  • AWS jobs were missing id-token: write, so assuming the role would fail
  • It ran the build three times (package, test, verify), now it's just mvn verify

Small stuff

  • Backoff is capped at 30s so a big attempt number can't overflow
  • Graceful shutdown on all the services
  • Email/SMS stubs throw if the simulation rates are negative or add up to more than 1
  • Correlation id header is only accepted if it looks like an id, otherwise we make a new one
  • JVM gets -XX:MaxRAMPercentage=75 in the images

Testing
Unit tests pass on JDK 25 locally. I don't have Docker on this machine so I couldn't run the integration tests or build the images. Those will run in CI for the first time here, so keep an eye on that. The deploy jobs also need the AWS role (OIDC) and the AWS_DEPLOY_ROLE_ARN / AWS_ACCOUNT_ID secrets set up, I didn't check that.

@marlware
marlware merged commit 553d301 into main Oct 13, 2026
3 checks passed
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