Repository navigation
Move to Java 25 and Spring Boot 3.5, fix CI - #1
Merged
Merged
Conversation
Let Hibernate create the schema and seed the demo users from data.sql, since migrations were more than this project needs. The README now explains why the project exists and reads less like a feature list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
CI
id-token: write, so assuming the role would failmvn verifySmall stuff
-XX:MaxRAMPercentage=75in the imagesTesting
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_IDsecrets set up, I didn't check that.