[
https://issues.apache.org/jira/browse/IO-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037780#comment-18037780
]
Benedikt Waldvogel commented on IO-881:
---------------------------------------
I could imagine that the impact of this issue is larger than you might expect.
It’s rather common to use automation tools to keep the dependencies up-to-date,
such as Renovatebot, Dependabot or Gradle’s "{{{}latest.release{}}}" with
dependency locking. Those automation tools fail now since they suggest to bump
the version to {{{}20030203.000550{}}}.
…even the version badge on [https://github.com/apache/commons-io] is currently
wrong ;)
!image-2025-11-12-16-31-57-683.png!
Wouldn’t it be possible to publish a new version, such as {{{}2.21.1{}}},
triggering a regeneration that fixes
[https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml?]
> 20030203.000550 is now latest version in Maven
> ----------------------------------------------
>
> Key: IO-881
> URL: https://issues.apache.org/jira/browse/IO-881
> Project: Commons IO
> Issue Type: Wish
> Affects Versions: 2.21.0
> Reporter: Alexander Veit
> Priority: Minor
> Attachments: image-2025-11-12-16-31-57-683.png
>
>
> With 2.21.0 the latest version in Maven has changed to
> `{color:#000000}20030203.000550{color}` which is wrong.
>
> See https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
