On repository.jboss.org I cannot close staging repository #19565 because it fails a check in 'jboss_releases_ruleset' 'Artifact Uniqueness Validation'

Event: Failed: Artifact Uniqueness Validation
Friday, September 09, 2022 15:06:59 CDT (GMT-0500)
typeId uniq-staging
failureMessage Artifact is not unique: 'org.wildfly:wildfly-oidc-feature-pack-galleon-common:27.0.0.Alpha4' in repository 'central' is same as '/org/wildfly/wildfly-oidc-feature-pack-galleon-common/27.0.0.Alpha5/wildfly-oidc-feature-pack-galleon-common-27.0.0.Alpha5.zip'
failureMessage Artifact is not unique: 'org.wildfly:wildfly-servlet-feature-pack-galleon-legacy:27.0.0.Alpha4' in repository 'central' is same as '/org/wildfly/wildfly-servlet-feature-pack-galleon-legacy/27.0.0.Alpha5/wildfly-servlet-feature-pack-galleon-legacy-27.0.0.Alpha5.zip'
failureMessage Artifact is not unique: 'org.wildfly:wildfly-ee-feature-pack-pruned:27.0.0.Alpha4' in repository 'central' is same as '/org/wildfly/wildfly-ee-feature-pack-pruned/27.0.0.Alpha5/wildfly-ee-feature-pack-pruned-27.0.0.Alpha5.zip'

What it's reporting is true, but it's not unexpected and isn't something problematic. The artifacts in question are simple zips of some content that often does not change from release to release. For example these are the same but there was no problem releasing these versions earlier this summer:

https://repo1.maven.org/maven2/org/wildfly/wildfly-servlet-feature-pack-galleon-legacy/27.0.0.Alpha2/wildfly-servlet-feature-pack-galleon-legacy-27.0.0.Alpha2.zip.sha1
https://repo1.maven.org/maven2/org/wildfly/wildfly-servlet-feature-pack-galleon-legacy/27.0.0.Alpha3/wildfly-servlet-feature-pack-galleon-legacy-27.0.0.Alpha3.zip.sha1

I can work around it at the cost of a day's effort and a release delay (which may prevent the project getting a new Jakarta EE certification in time to gain some favorable publicity.) It's also likely this will happen again for later releases, unless we change our software design simply to work around this rule.