County release jobs must name permits-portal artifacts from the SemVer Git tag that triggered the build. What should drive that naming?
Select an answer to reveal the explanation.
Short Explanation
You can use the triggering Git tag as the SemVer label for your release and permits-portal artifacts, keeping them traceable to their source. That linkage gives auditors and support staff a clear release trail.
Full Explanation
Git tag variables provide the SemVer identifier that triggered a release, so release and artifact-naming jobs should use that tag as their version input. For county permits-portal releases, the pipeline can stamp build outputs, container tags, or downloadable packages with the same version, creating a one-to-one trail from the immutable Git tag to the artifact auditors and support staff later retrieve. That linkage lets a citizen-facing portal build be traced to the tagged source that entered change control. Assigning fresh opaque names after packaging fails because it breaks the mapping between the SemVer tag and the package under test or in production, preventing auditors from proving which tagged commit produced a binary. Stripping version metadata and relying only on timestamps fails because clocks can collide or drift across runners, and timestamps do not encode SemVer intent or release lineage. Hard-coding v0.0.1 into every release job fails because all artifacts claim the same version, making promotions, rollbacks, and defect correlation impossible. Exam caveat: using the Git tag for naming is not the same as inventing a version in the job script or treating a mutable branch name as an immutable SemVer release identifier. Lightweight versus annotated tags and tag-creation protection still matter operationally; the focus is using the variable for the tag that triggered the release. Practical check: create a SemVer tag, run the release job, and confirm the artifact or image name embeds that exact string. Release with a different tag and verify the names differ; also confirm the artifact’s build metadata records the same tag for audit lookup.