Datex Studio CLI ยท Release notes

dxs 0.5.11

Release notes move to per-version pages, and skills documentation explains how add --all and update differ. The rest of this release is Datex staff tooling.

Released Oct 15, 2026 Previous 0.5.10 Merged PRs 2

Datex staff tooling

Datex

Needs a Datex staff identity. Nothing here changes anything for customers.
  • Atomic lifecycle updates and typed fieldsNew#309

    Use dxs devops update ID --expected-revision REV to change state, assignment and fields together. Create and update accept --field-json, --field-file and --fields-file for typed values and verbatim UTF-8 rich text. Updates also support field removal and field-only JSON Patch files.

    Omitted, empty, null and removed fields remain distinct. Azure DevOps enforces process rules; stale revisions fail with DXS-DEVOPS-CONFLICT. Read the latest item and reconcile before another update.

  • Raw evidence, history and commentsNew#309

    snapshot, workitem --raw and create --raw preserve original fields, HTML, identity objects, nulls and revisions, subject to credential redaction. history --kind updates or revisions and comments list provide paged evidence. Named collection commands fetch all pages by default; explicit limits report truncation and resume positions.

    Use comments add --project PROJECT --text-file FILE for an authorized comment. Existing --discussions reads now follow all update pages and report fetch failures.

  • Guard existing links and clean up one item at a timeNew#309

    relation list/add/remove selects exact link types and targets. Writes test existing link types and URLs as well as the revision, because link-only changes can leave the revision unchanged. Adding an existing link returns unchanged; ambiguous removals fail.

    delete ID --yes deletes the named item recoverably and never cascades to children. Lifecycle writes respect restricted mode and are never automatically replayed after an uncertain response.

  • Discover identities, team scope and process rulesNew#309

    identity resolves the effective DevOps caller or an assignee; assignment accepts me. teams and team areas/iterations/boards/board/backlogs/settings expose team scope, iteration dates and board state mappings. process --project PROJECT --type TYPE resolves inherited process references, fields, states and rules.

    devops api provides GET-only access to uncommon metadata with DevOps authentication and same-organization URL restrictions.

  • Skills and scripts using private Python DevOps clients: require CLI 0.5.11 or later and move to the supported commands. CLI 0.5.10 does not include this surface.
  • Scripts comparing exact fields: use snapshot or --raw; --full remains curated output. Use JSON or YAML for nested data, and inspect truncation/resume metadata on bounded reads.
  • Mutation callers: resolve the DevOps identity, use the observed revision and inspect saved state after an unknown outcome. Do not blindly repeat writes. Generic dxs api uses Studio authentication; use dxs devops api for DevOps metadata.

Behind the scenes

  • Versioned release notes and skills command guidanceDocs#310

    Historical notes now have per-version HTML pages, a shared template and an index. Skills documentation explains that dxs skills add --all refreshes existing skills and adds missing catalog skills; dxs skills update refreshes installed skills and their dependencies. A detailed command primer supports documentation authors.

Source record

Compiled from two feature/documentation PRs between v0.5.10 and v0.5.11: #309 and #310. This release's note preparation, version-bump and deploy-pin commits are excluded from that count. Dates use America/New_York.

PyPI package