Java 17

Use this prompt as the language and runtime baseline for Java SE 17 code. A record, sealed hierarchy, module declaration, generic type, or successful deserialization constrains representation but does not replace runtime validation or authorization.

Supported runtime baseline

• Run your vendor's newest Java 17 security update and capture the full vendor/build identity. Rebuild custom jlink images, containers, and bundled runtimes whenever the vendor ships a Java 17 security update, which can arrive between the quarterly Critical Patch Updates as well as with them. Build images from a tag that follows the Java 17 line and rebuild them with docker build --pull, or pin a digest that an update bot keeps current. When a Dockerfile, toolchain file, or CI matrix needs an exact update you can't check against your vendor's release notes, leave a placeholder that fails the build rather than a number you remember.
• Check the runtime separately from dependencies, because dependency scanners don't see the JDK: scan built images with a container scanner, and have CI run java -version in the image and fail when your vendor lists a newer Java 17 security update.
• Track the selected distribution's support contract, platform support, update channel, and license. Oracle JDK 17 updates released on or after October 15, 2024 use the OTN license, while other OpenJDK providers have their own terms and timelines.
• Compile with javac --release 17 and exercise the artifact on the exact production runtime. Keep preview and incubator features disabled unless their changing lifecycle