Skip to content

fix: pin FLASHBLOCKS env var names to preserve backward compatibility#485

Merged
avalonche merged 1 commit into
mainfrom
fix/flashblocks-env-var
Apr 29, 2026
Merged

fix: pin FLASHBLOCKS env var names to preserve backward compatibility#485
avalonche merged 1 commit into
mainfrom
fix/flashblocks-env-var

Conversation

@avalonche

@avalonche avalonche commented Apr 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Restore FLASHBLOCKS=true as the env var that enables the flashblocks WebSocket client, and defensively pin every other FLASHBLOCKS* env name so a future field rename cannot silently break the public env contract again.

Motivation

#373 renamed the field FlashblocksArgs::flashblocksFlashblocksWsArgs::flashblocks_ws and added id = "flashblocks_ws". clap derives the env-var name from id when env is left bare, so the public env var silently changed from FLASHBLOCKS to FLASHBLOCKS_WS. The CLI flag (--flashblocks) was preserved via explicit long = "flashblocks" but the env path was missed.

@vercel

vercel Bot commented Apr 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
rollup-boost Ignored Ignored Preview Apr 28, 2026 7:59pm

Request Review

@avalonche avalonche merged commit 9935598 into main Apr 29, 2026
7 checks passed
@avalonche avalonche deleted the fix/flashblocks-env-var branch April 29, 2026 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants