From f70ae02ee373cda787127e89f39810b33425c00a Mon Sep 17 00:00:00 2001 From: The-Big-Danny Date: Tue, 20 Oct 2026 07:05:58 +0100 Subject: [PATCH] docs(env): correct testnet migrate_adapter status in .env.example The note claimed the testnet vault lacked migrate_adapter; it was redeployed with it present and callable (#514, closed), per migration-keeper.md. Co-Authored-By: Claude Sonnet 5 --- .env.example | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.env.example b/.env.example index 66ebca02..92982021 100644 --- a/.env.example +++ b/.env.example @@ -42,9 +42,11 @@ MERIDIAN_MIGRATION_MIN_IMPROVEMENT_BPS=50 # per pool before it can report a rate, persisted via UPSTASH_REDIS_REST_URL # / UPSTASH_REDIS_REST_TOKEN above (falls back to an in-memory, per-process # store — not durable across serverless invocations — when those aren't -# set). The live testnet vault still doesn't have migrate_adapter deployed -# (see apps/docs/operations/migration-keeper.md, #514), so the keeper can't -# actually migrate anything on testnet yet regardless of these. +# set). The live testnet vault was redeployed with migrate_adapter present +# and confirmed callable (see apps/docs/operations/migration-keeper.md, +# #514, closed); nothing has actually exercised a real end-to-end migration +# against it yet, but these vars are no longer blocked on a missing entry +# point. MERIDIAN_ADAPTER_BLEND_ID= MERIDIAN_ADAPTER_DEFINDEX_ID=