This was introduced by #6023, but for some reason the CI runs on main used the build cache for wpilibj:compileJava and did not get this error, and since our checkout step only checks out the commit that triggered the CI run (the default for actions/checkout) and the PR was based on an old version of main that was still on Java 11, the PR CI runs were with Java 11, which does not have the warning.
I'm concerned about the fact that this could happen (CI runs pass but local clean builds fail), but I'm not sure what the best fix for the root cause would be. (Figure out why the build cache was reused? Figure out how to avoid issues from PRs based on stale versions of main?)
This was introduced by #6023, but for some reason the CI runs on
mainused the build cache forwpilibj:compileJavaand did not get this error, and since our checkout step only checks out the commit that triggered the CI run (the default for actions/checkout) and the PR was based on an old version of main that was still on Java 11, the PR CI runs were with Java 11, which does not have the warning.I'm concerned about the fact that this could happen (CI runs pass but local clean builds fail), but I'm not sure what the best fix for the root cause would be. (Figure out why the build cache was reused? Figure out how to avoid issues from PRs based on stale versions of main?)