Skip to content

Latest commit

 

History

History
118 lines (90 loc) · 3.72 KB

RELEASE_1.2.2_SUMMARY.md

File metadata and controls

118 lines (90 loc) · 3.72 KB

Release 1.2.2 Summary

Release Date

February 16, 2026

Overview

Version 1.2.2 is a patch release that fixes timezone and locale issues in the SatPassTime class, ensuring consistent behavior across all geographic locations and system configurations.

Changes

Fixed

  • Timezone/Locale Issues in SatPassTime (PR #6)
    • Date formatters now explicitly use Locale.US for consistent formatting
    • Timezone explicitly set to UTC for all date/time operations
    • Resolves test failures when running in non-US locales (e.g., Australian timezone)
    • Ensures consistent date/time display regardless of system locale settings

Technical Details

  • Added imports: DateFormatSymbols, Locale, TimeZone
  • Moved date formatter initialization to static initializer block
  • Applied explicit locale (Locale.US) to SimpleDateFormat instances
  • Set timezone to UTC for both TIME_FORMAT and DATE_FORMAT

Testing

  • ✅ All 149 tests pass
  • ✅ PassPredictorTest specifically validated (previously failing in Australian timezone)
  • ✅ No regressions introduced
  • ✅ Clean build with zero errors

Deployment

Maven Central

Artifacts

  • Main JAR: predict4java-1.2.2.jar
  • Sources JAR: predict4java-1.2.2-sources.jar
  • Javadoc JAR: predict4java-1.2.2-javadoc.jar
  • All artifacts signed with GPG

GitHub

Installation

Once published on Maven Central, users can update to version 1.2.2:

Maven

<dependency>
    <groupId>uk.me.g4dpz</groupId>
    <artifactId>predict4java</artifactId>
    <version>1.2.2</version>
</dependency>

Gradle

implementation 'uk.me.g4dpz:predict4java:1.2.2'

Impact

Who Should Upgrade?

  • High Priority: Users running applications in non-US locales
  • High Priority: International deployments (especially Australia, Europe, Asia)
  • Medium Priority: All users for consistency and future-proofing
  • Low Priority: US-only deployments (but still recommended)

Breaking Changes

None. This is a backward-compatible patch release.

Migration

No code changes required. Simply update the version number in your dependency configuration.

Next Steps

  1. Manual Publishing (Author action required)

  2. Verification (After publishing)

    • Verify artifacts appear on Maven Central
    • Test download and usage in a sample project
    • Update documentation if needed
  3. Communication

    • Announce release on GitHub
    • Update project website/documentation
    • Notify users of the fix

Credits

Related Links


Status: ✅ Ready for manual publishing on Maven Central Build: ✅ Successful (149/149 tests passing) Deployment: ✅ Uploaded to Maven Central staging Git: ✅ Committed and tagged (v1.2.2)