apiVersion: helm-expt.confighub.com/v1alpha1
kind: LatestCandidateReplacementDecision
metadata:
  name: bitnami-postgresql-18-7-0-defer-public-catalog-replacement
spec:
  chart: bitnami/postgresql
  currentVersion: 18.6.7
  currentSupportedVersion: 18.6.7
  currentSupportedBase: static-passwords
  candidateVersion: 18.7.0
  latestUpstreamVersion: 18.7.0
  candidateFreshness: latest-upstream-aligned
  candidateBase: static-passwords
  decision: defer-replacement
  decisionDate: "2026-06-10"
  catalogEffect: no-catalog-promotion
  targetScope:
    name: public-catalog-static-passwords-postgresql
    clusterClass: cub-lk-kind-vanilla
    namespace: postgresql
    deliveryPath: confighub-oci
    gitopsController: argo
  summary: "Keep bitnami/postgresql@18.6.7 as the supported public catalog version for now; retain bitnami/postgresql@18.7.0 as a proof-complete candidate."
  rationale:
    - "The PostgreSQL 18.7.0 candidate has render, ConfigHub, local live, and two-cluster live parity evidence for the static-passwords base."
    - "The current PostgreSQL 18.6.7 supported scope already has target-scoped public catalog support evidence."
    - "Replacing a supported stateful database base needs an explicit target-scoped support decision for generated credentials, storage, backup/restore, hooks, scan disposition, and target-fact policy."
  decisionTopicsReviewed:
    - "extension slot provenance and scan policy"
    - "generated fact ownership"
    - "hook and lifecycle phase policy"
    - "image digest support decision"
    - "scan/gate warning disposition"
    - "storage backup restore and rollback policy"
    - "target fact preflight"
  requirementsBeforeReplacement:
    - "Write a PostgreSQL 18.7.0 target-scoped production support decision with the exact stateful support boundary."
    - "Refresh ConfigHub OCI/Argo live evidence for the exact replacement scope after the candidate is selected."
    - "Refresh scan disposition and image-digest policy for the 18.7.0 rendered object set before treating it as the supported catalog version."
    - "Record whether PostgreSQL 18.6.7 remains a legacy patch/rollback reference after replacement."
  evidence:
    - path: data/production-support-decisions/bitnami-postgresql/support-decision.yaml
      claim: "Current PostgreSQL 18.6.7 supported scope remains the public catalog support decision."
    - path: recipes/bitnami/postgresql/18.7.0/catalog-status.yaml
      claim: "PostgreSQL 18.7.0 is visible as a catalog-candidate, not catalog-supported."
    - path: runs/latest-top20-refresh/postgresql-18.7.0/confighub-proof/latest/confighub-proof-receipt.yaml
      claim: "PostgreSQL 18.7.0 ConfigHub proof passed for the static-passwords base."
    - path: runs/latest-top20-refresh/postgresql-18.7.0/local-kind/observation-receipt.json
      claim: "PostgreSQL 18.7.0 local kind observation passed for the static-passwords base."
    - path: runs/latest-top20-refresh/postgresql-18.7.0/live-parity/static-passwords/receipt.yaml
      claim: "PostgreSQL 18.7.0 two-cluster Helm-vs-installer live parity passed for the static-passwords base."
    - path: data/production-disposition/receipts/bitnami-postgresql/generated-fact-ownership.yaml
      claim: "Generated fact ownership is an explicit replacement topic for this chart."
    - path: data/production-disposition/receipts/bitnami-postgresql/hook-and-lifecycle-phase-policy.yaml
      claim: "Hook and lifecycle phase policy is an explicit replacement topic for this chart."
    - path: data/production-disposition/receipts/bitnami-postgresql/storage-backup-restore-and-rollback-policy.yaml
      claim: "Storage backup, restore, and rollback policy is an explicit replacement topic for this chart."
    - path: data/production-disposition/receipts/bitnami-postgresql/target-fact-preflight.yaml
      claim: "Target fact preflight is an explicit replacement topic for this chart."