Version check reports an older release as “new version available”

[shihyuho]

Environment:

• Jib version: 3.5.0
• Build tool: Maven
• OS: Mac Tahoe 26.1

Description of the issue:

When using jib-maven-plugin version 3.5.0, the plugin reports that 3.4.6 is a newer version:

[INFO] A new version of jib-maven-plugin (3.4.6) is available (currently using 3.5.0). Update your build configuration to use the latest features and fixes!
[INFO] https://github.com/GoogleContainerTools/jib/blob/master/jib-maven-plugin/CHANGELOG.md
[INFO]
[INFO] Please see https://github.com/GoogleContainerTools/jib/blob/master/docs/privacy.md for info on disabling this update check.

This is incorrect, because 3.4.6 is older than 3.5.0.

Expected behavior:

The plugin should not report an older version as the latest available version.

[Gautam-aman]

Hi, I'd like to work on this.

Plan:

• Fix the update-check logic so version comparison uses semantic versioning (3.5.0 > 3.4.6).
• Add/update tests for the version comparison.
• Verify that 3.5.0 does not report 3.4.6 as newer.

If this looks good, I’ll open a PR.

[codingkiddo]

Hi maintainers, I’d like to work on this issue.

From a first look, UpdateChecker currently suppresses the update message only when the current version exactly equals the remotely reported latest version. That means a stale remote value such as 3.4.6 can still be reported while running 3.5.0.

My proposed approach:

• Add a regression test where currentVersion is 3.5.0 and the remote latest value is 3.4.6
• Update the check so it only reports an update when the remote latest version is actually greater than the current version
• Keep the existing behavior for a true newer version such as current 3.4.6 and latest 3.5.0

Would this approach be acceptable? If yes, could this issue be marked Accepting Contributions?