Repository navigation
The first M2 release: failures are drawn as diagnostics and run progress live on a
terminal, the Databricks provider signs in to the workspace (ods doctor --connect),
secret references are resolved by secret providers, producing code can be referenced
and retrieved, and the crates are published to crates.io. Releases are cut with
rab. Nothing here breaks a script; unknown Databricks settings are deprecated.
0.1.2 was prepared (its version and notes were merged on 2026-11-03) but never
published; its changes are in this release, under Changed.
Added
- The crates are published to crates.io with each release, at the release's version
(ADR-0035):ods-cli(cargo install ods-cliinstallsods), the SDK, the modules and the providers, so Rust tools can
use ODS's types, such asods-erd's ERD model, and plugin authors can build against
ods-sdk. - The Databricks provider can sign in to the workspace itself (#297,
ADR-0021, now accepted): with a
service principal's OAuth secret (auth = "m2m", narrowest scope first) or a static
token (auth = "pat"). Secrets are references, tokens stay in memory, and only
HTTPS hosts are used. ods doctor --connectsigns in to the warehouse for each provider that setsauth
(connectivity.warehouse_login, #297) and shows the method, principal, scopes,
expiry and whether it was verified, never the token. New codes:ODS-E0608(can't
be set up),ODS-E0609(refused),ODS-E0610(unreachable),ODS-U0611(a static
token, not verified). Without--connectthe check is skipped, like the other live
checks.- Warehouse plugins can sign in (
WarehousePlugin::credentials);ods plugin list,
ods versionandods doctorlist it for Databricks assign_in(credentials
contract). - SDK 0.11: the
credentialscontract 0.1 (how a provider signs in, never its token),
its conformance suite (ods_sdk::conformance::credentials) andFakeCredentials. - Secret references are resolved by secret providers, one per scheme (#126,
ADR-0032).env:is built in. A customods
adds others, such as an OS keychain or a cloud secret store, with
Ods::secret_provider. A value is resolved only where its credential is used, kept
in memory for that use alone, and never written to configuration, state, logs or
output; a missing or empty secret is an error, never an empty credential.
Nothing reads a credential through them yet: Databricks authentication (#297) is
the first. ods version,ods plugin listandods doctor(capabilities.plugins) list
secret providers,envamong them.- SDK 0.10: the
secret_providercontract 0.1, its conformance suite
(ods_sdk::conformance::secrets) andFakeSecretsinods-provider-fake. - Provider-neutral producing-code references, scoped declared mappings and a dbt
source metadata adapter (part of #462,
ADR-0033). Metadata lookup only; process-plugin
transport is not yet implemented. Local retrieval is available through the separate
reader contract. - Opt-in immutable code retrieval through a provider-neutral reader and approved
local Git repositories or credential-free HTTPS fetches, with run/revision
checks, byte limits and deadlines (part of #462,
ADR-0034). No push API or
worktree source reads; private authentication requires read-only credentials.
Changed
- The docs site is built with Zensical, the successor to Material for MkDocs, in place
of MkDocs and Material (zensical.tomlreplacesmkdocs.yml;
python -m zensical serveto preview). Its pages, links and look carry over, with
Zensical's header and search. - On a terminal, failures are drawn as diagnostics (#447):
error[code]: what failed,
the file it is about (--> models/….sql), thennote:andhelp:lines with the
same redacted facts as before. When several nodes fail, a summary by file comes
first. An error ODS reports itself is drawn the same way, its hint ashelp:.
Plain and JSON output, and what the MCP tools return, are unchanged. - On a terminal,
ods state build(andrun,seed,snapshot,compile) draws
its progress live (#446): each dbt command and its nodes in a tree redrawn in place,
dbt's lines printed above it, and a summary of the nodes (succeeded, failed, skipped)
when the run ends. Piped or redirected, and with-qor-v, progress is the plain
ods ▸lines it was. The report, JSON output, run events and journal are unchanged. - Releases open a pull request on the Homebrew tap with the new formula, so
brew upgrade odsgets each release once that is merged (maintainers set up a token:
see "For maintainers" indocs/install.md). - Releases are cut with rab, the Release Asset Bundle
(ADR-0019 §5). The GitHub release, itsvX.Y.Ztag, its archives,SHA256SUMS,
attestations andods.rbare as before, but wheels are now on PyPI only, not
attached to the GitHub release, andcargo binstall ods-clifinds the archives from
crates.io. The Homebrew formula and the Chocolatey package are made by rab
from the same templates. Maintainers: see "For maintainers" indocs/install.mdfor the new
crates-ioenvironment and therelease-*tags.
Deprecated
- An unknown setting under a
[providers.<name>]withkind = "databricks"is still
ignored, but now with a warning on stderr that names it; from 0.2.0 it is a
configuration error (ODS-E0102). Fix or remove the key the warning names. The
settings are listed in docs/databricks.md (#297).
Install
pip install opendatasuite==0.1.3 # or: pipx install / uv tool install opendatasuite
cargo binstall ods-cli@0.1.3 # a prebuilt binary; or: cargo install ods-cli@0.1.3 --lockedHomebrew, Chocolatey, direct downloads and verification (SHA256SUMS, build provenance):
https://buchochelliq-labs.github.io/open-data-suite/install/