Tags give the ability to mark specific points in history as being important
-
v1.4.0
protectedRelease: pipeline v1.4.0a8fc49b0 · ·v1.4.0 Three Go-focused components: - go-build: branch verification cross-compile (matrix of GOOS/GOARCH, version-from-ref ldflags). Skipped on tags. - go-release-binary: tag-only build, sha256 checksums, cosign keyless signing via GitLab OIDC, upload to the project's generic package registry. - release-create: tag-only GitLab Release creation with annotated tag message + asset linking from the package registry. Together these enable a full branch-and-tag CI shape for any Go project in the dunn.dev estate. First consumer: dunn.dev/bairn. Modeled on the binary + release templates in gitlab.com/gitlab-com/public-sector-tools/pipeline (Apache 2), scaled down to the dunn.dev estate's needs (no SBOM, no SLSA attestation; those layer on later if a project needs them). Existing components (claude-drift-triage, cloudflare-pages, cloudflare-r2, cloudflare-worker, container-image) ship at v1.4.0 unchanged.
-
v1.3.0
protectedRelease: pipeline v1.3.00d04dfaf · ·v1.3.0 — claude-drift-triage component Adds claude-drift-triage to the catalog. LLM-augmented schema drift triage: a consumer's drift command emits diffs; the component sends them to Claude for classification and concrete next-step suggestions; optionally opens a GitLab issue with the triage. No breaking changes; existing components unchanged. CI image unchanged (curl + jq + bash already present). Validated via glab api ci/lint against a synthetic consumer (see commit 0d04dfa).
-
v1.1.0
protectedRelease: pipeline v1.1.0a38d1c02 · ·default to shared CI image, image input on all components
-
v1.0.0
protectedRelease: pipeline v1.0.0ecf0591b · ·initial release: cloudflare-pages, cloudflare-worker, cloudflare-r2, container-image