v1.2.0 — Disabled catalog refresh schedules

Adds a standalone chart for independent six-hour catalog checks. Every source is opt-in, the chart defaults disabled and suspended, and no watched ArgoCD Application references it. Existing home resources and deployment pins are unchanged.

Jobs have source-specific UTC staggering, overlap protection, hard runtime/retry/resource bounds and the existing database custody. Optional rules use the backend's durable health to report missed checks, failures and pending human review. Installation, imports, metrics enablement and unsuspension remain separate operational actions.

Validation: 74 complete GitOps contract tests passed, including four new scheduler tests; both charts lint and default/home umbrella renders pass. Self-review and diff checks passed. No cluster actions.

Release: 1.1.0 -> 1.2.0 (MINOR). New compatible opt-in chart functionality; prior unreleased changes are documentation only. Publish a GitHub Release on reviewed main; do not change runtime pins or install the scheduler.

v1.1.0 — stable pre-refactor checkpoint

Stable pre-refactor checkpoint

September 22, 2026. This release preserves the existing Driftplain project before the benchmark-explorer and CI-selection refactor. It does not implement that refactor.

Repository commit: 8f38c042dff87df8058616c66ee7271bd335bcda. The tag is an immutable source checkpoint; no application code or runtime configuration was changed for this release.

Coordinated component versions

Repository	Tag	Commit
driftplain-backend	v1.1.0	270b4d0a1b89fe1ab8a7a69103837e7a45529e2b
driftplain-frontend	v1.1.0	6d902996090a55faa251d497bd86d19424f3ea8c
driftplain-gitops	v1.1.0	8f38c042dff87df8058616c66ee7271bd335bcda
driftplain-infra	v1.1.0	af06662812014d843d0fda3daaf520bc252a8e8e

Deployment and recovery

The app continues running on the home Kubernetes cluster. Existing GitOps image digest pins remain unchanged. Backend/frontend tags trigger image publication only; deployment requires a separate GitOps change.

Use the coordinated source tags for an interview checkout. For a runtime rollback, use the tagged GitOps home profile and its pinned images, and verify database compatibility or restore through the infrastructure recovery runbook. A Git tag is not a database backup. Do not apply the retired AWS platform as a rollback shortcut.

Existing historical v1.0.0 tags remain unchanged. The temporary unprefixed 1.0.0 checkpoint created during this session was replaced by v1.1.0.