v0.15.0

This release adds the Alteryx One cloud-native workflow surface and expands endpoint-coverage reporting.

Highlights

ayx one workflows

Cloud-native canvas workflows are now a first-class CLI surface. list, count, assets, detail, dependencies, engines, tools, copy, and share operate on ULID-keyed workflows served by /svc-workflow/api/vN. These are not one flows, which remains the integer-id-keyed Designer Cloud /v4/flows family; a workspace can contain many cloud-native workflows while one flows list returns no items.

detail and count are synthesized client-side because the service has no per-id or count route. Their envelopes identify the source with detail_source and count_source. share resolves person email addresses before building its body; its request shape was recovered from service schema-validation errors rather than a published specification. Authoring arbitrary visual workflow logic remains out of scope because no public endpoint accepts it.

API coverage outside the /v4 namespace

ayx one api coverage now reports wired endpoints outside the One gateway spec namespace. The /svc-workflow, /plans/v1, /scheduling/v1, /billing/v1, and /iam/v1 rows now appear under outside_spec_namespace, inventory_total counts every distinct wired row, and coverage_pct is explicitly scoped to the comparable namespace. --check still gates only on missing.

Breaking changes

Agent-facing JSON from ayx one api coverage --output json changed shape. stale[].command (a string) is now stale[].commands (an array), because one endpoint can serve multiple commands. coverage_pct is nullable and becomes null when there is no comparable spec data. Consumers must handle the new inventory_total and outside_spec_namespace fields and update any parser that reads the old field.

Other changes

• The endpoint drift gate now scans src/main.rs as well as src/cmd/**, covering dispatchers that live in the main binary.
• Server API failures preserve the structured error_code classification computed from their HTTP status.
• 410 Gone and additional status classes now map to actionable not_found, permission_denied, conflict, or network codes; transport failures no longer masquerade as empty successful lists.
• Fixed the live route for one connections permissions and restored the dry-run gate for one output-objects wrangle-to-python.
• one workflows list --all now reports complete: true/false and warns on stderr instead of silently returning a partial result — /v4/workflows has no real cursor pagination.
• ayx actions export --output json now produces valid, parseable JSON; the YAML moved into the envelope’s data.yaml field.
• Release builds now surface missing macOS signing configuration, with AYX_REQUIRE_MACOS_SIGNING=true available to make it a hard failure. README and getting-started docs include the current Gatekeeper workaround.
• All workspace crates declare repository and homepage metadata.