Clearer validation errors in the Turbo pipeline editor
Follow @goldskyio on Twitter to stay updated on everything we ship.
The Turbo visual editor now shows the actual validation error when a pipeline config has a problem, instead of a generic "Invalid Pipeline Configuration" message.
Every Turbo pipeline is now validated before it's applied, so mistakes surface in the editor before anything reaches production. Block ranges get checked too: end_block can't be 0, and start_block has to come before end_block.
Paused pipelines pick up new secrets on resume
Rotated a database password or API key? Update the secret and resume the pipeline. Turbo now reloads secrets when a pipeline resumes, so you no longer need to recreate the pipeline to use new credentials.
- Added chain support: LitVM LiteForge Testnet (Subgraphs)
- Added fee and fee decimals fields to the token transfers dataset
- Sources and sinks now preload in the Turbo editor, so they are ready the moment you drop them on the canvas
- Deploy errors now show the underlying cause when a sink fails to load
- Block lag for Turbo pipelines is now measured before filters run, for a more accurate reading
- Dashboard search now returns Quick Actions, so searching "create" or "settings" takes you straight there
- Fixed the pipeline size dropdown not updating the YAML
- Fixed long secret names overflowing the sink configuration panel
- Fixed the new project modal staying open after you create a project