Release information

Documentation baseline: September 6, 2026

The documentation was reorganized around onboarding, workflows, integrations, API contracts, workspace configuration, and production operation. Public examples and limitations were reconciled against the application, SDK, CLI, and node implementations.

The published OpenAPI document describes the customer integration surface. Platform administration and provider-operated callbacks are not customer integration endpoints. Internal architecture and deployment runbooks are maintained separately from this site.

Check compatibility before upgrading

1. Record dagy --version and your installed dependency versions.
2. Review the OpenAPI reference for changed requests, responses, and validation rules.
3. Check limits and the selected node's entry for availability and execution caveats.
4. Exercise your integration in a development environment, including failure and retry behavior.
5. Promote the tested version and verify environment configuration and dependency packages.

The current API has no built-in /v1 path prefix. Preserve your deployment's supplied base path. Do not invent an API version selector or assume source version 0.1.0 establishes a long-term compatibility guarantee.

Compatibility notes

Use current runtime names nano, micro, small, medium, large, and xlarge; older aliases remain accepted as described in runtime selection. CLI parameter typing, local/hosted behavior, and credential configuration are documented in the CLI reference.

No historical product release dates or feature launch claims have been reconstructed from incomplete documentation. Future externally visible changes must add a dated entry here, explain the impact and migration action, and update the affected guides and references in the same change.