v0.5.0

Added

• tx bpa run --fix --dry-run previews fixes without changing the model. Each pending fix is
  listed as Would fix: (or Would delete: with --allow-delete) with the property's value
  before and after, followed by how many findings would remain. Nothing is applied, saved, or
  staged, and the exit code still follows --fail-on for the model as it is. JSON adds
  dryRun, fixesPending, wouldRemain, and a fixes array with each fix's before and after
  values; outside a dry run, fixes lists the fixes that were applied (#268).
• tx connect <workspace> --list lists the semantic models on a workspace or XMLA
  endpoint without connecting (name, compatibility level, last update). It works
  non-interactively and with --output-format json, so scripts and agents can
  discover models on a workspace that hosts more than one.
• tx refresh reports refresh progress in detail: a live panel shows overall progress and each
  in-progress table's step (querying, reading, compressing, hierarchies, calculated columns),
  partition, rows, and running time, then the model-level steps (relationships, calculation
  script, commit). It replaces the single status line, which on large models was cut off at the
  terminal width and kept showing the same few tables. The summary adds a Process
  column, a row per partition for multi-partition tables, and a phase table; JSON gains
  tables[].processMs, tables[].partitions, and phases.

Changed

• Opening a workspace that hosts several models without naming one now fails with
  TOMIX_DATABASE_REQUIRED (exit 2) and a hint to run tx connect <workspace> --list,
  instead of TOMIX_CONNECT_FAILED / TOMIX_QUERY_FAILED (exit 1).

Removed

• Breaking: tx query --plan and the plans field of tx query --output-format json. Power BI /
  Fabric XMLA endpoints never deliver query-plan trace events, so the option could not return a plan.

Fixed

• tx refresh reported only the last partition's rows and timings for tables with several
  partitions, and on Power BI / Fabric could summarize before the trace arrived, reporting zeros
  (typically with --output-format json).
• tx query --trace returns server timings on Power BI / Fabric XMLA endpoints. The trace was
  rejected for an unsupported column, and events that arrived were then silently discarded; timings
  (and benchmark storage-engine stats) came back null. A missing timing now always comes with a
  warning on stderr.

What's Changed

• ci: automate releases with verified previews and a release PR by @bgarcevic in #315
• feat(connect): list models on a remote workspace with --list by @bgarcevic in #316
• fix(query)!: restore Fabric trace timings, detail refresh progress, remove --plan by @bgarcevic in #318
• feat(bpa): --dry-run for --fix previews fixes without applying them by @bgarcevic in #319
• chore(release): prepare 0.5.0 by @github-actions[bot] in #317

New Contributors

• @github-actions[bot] made their first contribution in #317

Full Changelog: v0.4.3...v0.5.0