Can ZoneId Resolution Guarantee Consistent Offsets Across Java Versions?

Converting a LocalDateTime to a ZonedDateTime using an IANA time‑zone identifier aims to produce the correct wall‑clock offset for the specified region.

The conversion requires an explicit ZoneId; without it an exception is thrown and the offset depends on the TZ database version bundled with the JVM.

Can the same ZoneId yield different offsets on Java versions with different TZ database releases? How does the runtime handle DST rule changes when the TZ data is outdated?