v0.6.0

Fixed

• tx validate no longer reports every column reference into a calculated table as missing
  (DAX0002) when its TMDL declares no columns because the table was never evaluated. Columns
  are inferred from DATATABLE(...) and ROW(...) expressions, so typos are still caught;
  references into calculated tables whose columns cannot be inferred offline are not judged (#320).
• tx validate in CI logs: with --ci (or under Azure Pipelines), findings are no longer
  hard-wrapped at 80 columns, so each one stays on its own line. In Azure Pipelines, a column
  named like a log command ([Group], [Section], [Error], ...) no longer turns its line
  into a collapsible section header that drops the ##[error] styling and leaves stray 8m
  fragments in the table.
• tx validate no longer warns (DAX0003) about columns an expression defines for itself:
  [@Name] when "@Name" is a new column's name in ADDCOLUMNS, SELECTCOLUMNS,
  SUMMARIZE, SUMMARIZECOLUMNS, GROUPBY, ROW, or DATATABLE, and [Value] from
  GENERATESERIES or a { ... } table constructor (not an IN { ... } list).
• tx validate now checks where those columns are used: a column an expression builds is
  accepted only where a row of its table is in context (inside FILTER, SUMX, and other
  iterators over it, also through a VAR), and a use outside it warns with DAX0003 "is built
  by this expression but used outside the table that has it".

What's Changed

• fix(validate): infer columns of undeclared calculated tables by @bgarcevic in #320
• docs(changelog): move #320 entry to [Unreleased] and document the rule by @bgarcevic in #321
• fix(validate): readable CI logs and no warnings for query-scoped columns by @bgarcevic in #323
• fix(validate): scope-check columns an expression builds itself by @bgarcevic in #324
• chore(release): prepare 0.6.0 by @github-actions[bot] in #322

Full Changelog: v0.5.0...v0.6.0