Release v2026.08.19 for a library catalog API must be auditable across Git and the deployment pipeline. Which release-management practice meets that need?
Select an answer to reveal the explanation.
Short Explanation
Auditors want a name on the jar: Git tag plus pipeline label for v2026.08.19. Floating "latest" and chat-only notes are how civic release history vanishes when someone asks what shipped Tuesday.
Full Explanation
Labels, branches, and tags support version and release management by tying a named release to a specific commit and pipeline run. Immutable or clearly versioned tags improve auditability for production changes. Relying on unlabeled feature-branch deploys, overwritten floating tags, or informal chat notes weakens traceability.