Skip to content

docs(env): correct testnet migrate_adapter status in .env.example #1205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
collinsezedike merged 1 commit into from
Oct 20, 2026
Merged

docs(env): correct testnet migrate_adapter status in .env.example #1205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions .env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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=

Expand Down
Loading