Add optional Antora versioning controls

[jruaux]

Summary

• add optional checkout depth/tag inputs to the reusable docs workflow
• add optional Antora version, display version, and prerelease inputs to the reusable release flow
• extend the update-antora-version action to write optional display/prerelease metadata

Compatibility

Defaults preserve the current behavior for existing consumers.

---

Note

Low Risk
Low risk workflow/action changes that are opt-in and default to existing behavior; main risk is misconfiguration of new inputs affecting docs versioning during release/deploy.

Overview
Adds optional Antora versioning controls to the release automation. The update-antora-version composite action can now also set display_version and prerelease in docs/antora.yml (updating existing keys or appending them when missing), and release.yml exposes inputs to override the version used plus pass through these new fields.

Extends the reusable docs.yml workflow to accept checkout fetch-depth and fetch-tags inputs so callers can fetch full history/tags when Antora needs tag/branch discovery.

^{Written by Cursor Bugbot for commit be8df16. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

Missing leading newline in prerelease printf append

Low Severity

The printf for appending prerelease omits the leading \n that the display_version printf includes. If docs/antora.yml doesn't end with a trailing newline and only prerelease is being appended (no display_version), the prerelease: key gets concatenated onto the last line of the file, producing invalid YAML. The format string here likely needs '\nprerelease: %s\n' to match the display_version pattern.

Additional Locations (1)

• .github/actions/update-antora-version/action.yml#L47-L48