From 097da2e4ff69556d2b96b5f59acb4f622b672dfb Mon Sep 17 00:00:00 2001 From: Nandan Rao Date: Wed, 26 Aug 2026 19:46:41 -0400 Subject: [PATCH] chore(prod): adopt v0.1.79, swoosh v0.1.11 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ships the ref-mode work (#247). The dashboard half is already live — Netlify deploys from main on merge — so production is currently serving an Ad Attributions step whose endpoint adopt v0.1.78 does not have, and an extraction form offering `variable` + `ad_table_lookup`, which v0.1.78 rejects at save. This closes that gap. Both images are inert against production data, verified against vprod rather than assumed: 0 of 719 destination confs carry ref_mode or include_metadata_in_ref, so all 719 resolve to "metadata" and creatives stay byte-identical — vlab-adopt-ads should generate zero instructions on its next run. 0 of 691 inference confs declare a mapping, so no event produces an ad outcome, exactly as today. No migration: this change adds no SQL, and ad_attributions plus its ref_token column are already live at 20260818000000. migrations stays v0.2.0. Co-Authored-By: Claude Opus 5 (1M context) --- devops/values/toixo-prod.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devops/values/toixo-prod.yaml b/devops/values/toixo-prod.yaml index 8254470c..9900e293 100644 --- a/devops/values/toixo-prod.yaml +++ b/devops/values/toixo-prod.yaml @@ -1,4 +1,4 @@ -versionAdopt: &vadopt v0.1.78 +versionAdopt: &vadopt v0.1.79 # Schema migrations. The pre-upgrade hook (devops/helm/templates/migrations.yaml) # runs this image's `migrate up` against the DB below before new pods roll. @@ -127,7 +127,7 @@ cronjobs: schedule: "30 * * * *" image: repository: "ghcr.io/vlab-research/swoosh" - tag: "v0.1.10" + tag: "v0.1.11" pullPolicy: Always - name: adopt-ads schedule: "30 */2 * * *"