Antora failure: Duplicate version detected #53
Description
When branches and tags are pushed together (as with update-scheduled-release-version.yml), Antora failures occur due to both a branch and tag pointing to the same version number simultaneously.
[18:29:10.345] FATAL (antora): Duplicate version detected for component security: 6.4.0-RC1
Cause: Error
at ContentCatalog.registerComponentVersion (/home/runner/work/spring-security/spring-security/node_modules/@antora/content-classifier/lib/content-catalog.js:85:15)
at registerComponentVersions (/home/runner/work/spring-security/spring-security/node_modules/@antora/content-classifier/lib/classify-content.js:38:34)
at GeneratorContext.classifyContent (/home/runner/work/spring-security/spring-security/node_modules/@antora/content-classifier/lib/classify-content.js:25:24)
at /home/runner/work/spring-security/spring-security/node_modules/@antora/site-generator/lib/generate-site.js:30:18
at async Promise.all (index 0)
at async generateSite (/home/runner/work/spring-security/spring-security/node_modules/@antora/site-generator/lib/generate-site.js:25:5)
at async Command.parseAsync (/home/runner/work/spring-security/spring-security/node_modules/commander/lib/command.js:1092:5)
If we omit pushing the tag when the release commit is pushed, the branch can be tagged later which will separate pushing a release commit to trigger a release from tagging a release once it is finished.
NOTE: The gradle task createGitHubRelease that is called after the release has succeeded will automatically tag the release if it has not been tagged already, which will trigger the full docs build automatically.