Skip to content
VAIF Studio Docs
By meaning

Changelog

Changes to VAIF Studio that affect how you build, newest first. A change marked Breaking needs a change in code that worked before. For the SDKs, each SDK page shows the current version and whether it can be installed.

10/22/2026: Write-only secrets, alert rules by plan, and production writes from the CLI and MCP

Secret values can be replaced but never read back. The number of alert rules per project follows your plan, and the CLI and the MCP server need an explicit flag before they write a production secret.

  • Breaking: The routes that returned a secret value are removed: GET /functions/secrets/{secretId}/value and GET /projects/{projectId}/env-vars/{envVarId}/value. vaif secrets get now explains that values are write-only and exits with status 1. Replace a value with vaif secrets set.
  • vaif secrets set and vaif secrets delete take --allow-production, and the MCP tools set_secret and delete_secret take allow_production. Both are off by default. A production secret write needs the flag and an owner or admin.
  • A variable or function secret created with envId: null applies to every environment, production included, so creating one is always a production write.
  • Alert rules per project follow your plan; see Plans. Creating one past the limit answers 403 with the code ALERT_RULE_LIMIT.