v0.16.0
v0.16.0 makes the versioned Wizard authentication orchestration the default
rollout for ayx one login. The legacy email-OTP adapter remains available as
an explicit rollback path.
Authentication
Section titled “Authentication”- Wizard login now uses the binding-aware profile and credential persistence path by default.
- Existing legacy, unbound keyring references remain readable.
AYX_AUTH_ROLLOUT=legacyrestores the legacy adapter if a live regression requires rollback.- Regional One hosts remain explicit configuration: pass the workspace’s
actual
https://<region>.alteryxcloud.comURL rather than assumingus1. - Secure keyring persistence remains preferred; session-only and explicit consent-based plaintext fallback remain available for constrained hosts.
Alteryx One API
Section titled “Alteryx One API”- The release includes the verified One surface repairs from the v0.15.0
development cycle: corrected
/v4route families, dataset filter handling, workflow pagination, mutation dry-run protection, and honest API coverage reporting. - The live baseline is documented at 63.1% comparable operation coverage: 147 covered of 233 spec operations, with 86 missing, 16 stale, and 7 outside-spec operations. The remaining gaps are roadmap work, not a release blocker.
one person countremains deprecated because the vendor endpoint returns HTTP 410 Gone.
Platform and release posture
Section titled “Platform and release posture”- Windows, WSL2/Linux, and the macOS core cross-target checks are covered by the release validation evidence. Full macOS API compilation still requires an Apple SDK/CI host.
- macOS release artifacts are published unsigned when signing/notarization secrets are unavailable; the release workflow emits an explicit warning.
- See the public release checklist and the production authentication handoff for validation and rollback procedures.