Tags give the ability to mark specific points in history as being important
-
v1.3.1
d8c5d881 · ·v1.3.1: inject catalog v1.6.1 The injected stage file pins the catalog release carrying the corrected container image-signature check, and the Pipeline Execution Policy pins this release as its content. Both pins move together: the policy reads this project's default branch, so a content ref that names a tag which does not yet exist stops pipeline creation on every governed project.
-
v1.3.0
242e2e91 · ·v1.3.0: five stations injected, and the export goes central policy-content/conformance-stage.yml pins the catalog at v1.6.0 and no longer includes the export component. An export in .pipeline-policy-post is skipped whenever a station fails, so it never reached the red consumers; a scheduled job on gitlab-profile now runs `factory export --source pull` against each consumer's latest pipeline whatever its status, and is the only writer of boe/authorization.
-
v1.0.0
7fc29696 · ·quality-control v1.0.0 — the policy plane, pinnable First tagged release, cut so the Pipeline Execution Policy can pin the content it injects instead of tracking main. Carries the qc: line injection, the phase-scoped approval ratchet, the two classifier gates, and the baseline scanner rung.