Skip to main content
Workflow builder: vault secret bindings removed.
  • Produce and procedure nodes in the workflow builder no longer show a Secret Bindings section, and Workflow Settings no longer shows Default Vault. Nothing read those bindings when a workflow ran, so a vault secret picked there never reached the agent, tool or procedure.
  • Secrets reach agents, tools and procedures through Credentials, which checks each credential’s approval and expiry. A procedure node keeps its credential binding in the builder.
  • Vaults and Environments are unchanged: they hold secrets and push them to deployment targets.
Workflows: vault secret binding fields removed.
  • Workflow nodes no longer have a secretBindings field, drafts and versions no longer have defaultVaultId, and runs no longer have vaultOverrides. All of them were already empty, and nothing read them when a workflow ran.
  • Secrets reach agents, tools and procedures through Credentials, which checks each credential’s approval and expiry.
Workflows: vault secret bindings no longer stored.
  • Saving a workflow node no longer stores vault secret bindings, saving workflow settings no longer accepts a default vault, and publishing no longer copies one onto the new version. Bindings already stored are cleared on the next deployment. Nothing read them when a workflow ran, so no run changes.
  • Secrets reach agents, tools and procedures through Credentials, which checks each credential’s approval and expiry.
  • Vaults and Environments are unchanged.