You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java 17 is now the minimum required runtime — Projects still on Java 11 or earlier will fail to build or run pds4-jparser v3.1.0+. Upgrade your JDK and update any CI/CD pipelines accordingly before adopting this release.
(#180)
Highlights
Java 17+ is now required; update your JDK before upgrading (#180)
PDS4 Information Model upgraded to version 1Q00, bringing support for Product_Resource and other new product types (#195)
All outbound URL connections now enforce HTTPS, closing a long-standing security gap (CWE-311) (#191, #190)
Fixed a BigInteger/int type mismatch in image exporters that arose after the 1M00 IM upgrade (#194)
Label parsing now uses a local schema file fallback instead of attempting to download remote URLs, improving reliability in offline/restricted environments (#189)
New
PDS4 IM 1Q00 support: Upgraded the bundled Information Model schemas to 1Q00. New product types (e.g. Product_Resource) are now fully parsed and dispatched; an IM upgrade procedure is documented in CLAUDE.md for future maintainers. (#195, #192)
Improvements
Label parsing falls back to a local cached schema file instead of fetching remote URLs, increasing robustness in network-restricted environments (#189, #188)
Fixes
AxisArray.getSequenceNumber() no longer fails to compile after upgrading from IM 1L00 to 1M00 (#193)
BigInteger/int type mismatch in image exporters resolved following the 1M00 IM upgrade (#194)
Security
All outbound connections in URLUtils now enforce HTTPS, addressing CWE-311 (cleartext transmission of sensitive information) — a fix that was pending since v2.9.0 (#191, #190, #44, #14)
Compatibility
Requires: Java 17 or higher (upgraded from Java 11 — see Breaking Changes above)