|
| 1 | +# v0.1.11 |
| 2 | + |
| 3 | +_Released: 2026-08-07_ |
| 4 | + |
| 5 | +Headline: `tycoon.yml` learns its **own schema version**. The ingestion |
| 6 | +rewrite's second milestone lands — `runtimes:` and `metadata:` blocks on |
| 7 | +the project model, an integer `schema_version` with comment-preserving |
| 8 | +in-place migration via the new **`tycoon init --upgrade`**, and the |
| 9 | +config singleton replaced across the ingestion commands. Alongside it: |
| 10 | +a pinned, fully-formatted codebase and the first release-time |
| 11 | +dependency review. |
| 12 | + |
| 13 | +## Landed |
| 14 | + |
| 15 | +- **A versioned, migratable `tycoon.yml`** (#83, PR #190) — the project |
| 16 | + file now carries `schema_version` (an integer, currently `2`) plus |
| 17 | + `runtimes:` and `metadata:` blocks, both defaulted so existing files |
| 18 | + load unchanged. `tycoon init --upgrade` migrates older files in |
| 19 | + place — idempotent, and your comments, blank lines, and own |
| 20 | + `version:` field survive untouched (ruamel.yaml under the hood). A |
| 21 | + stale file warns and names the remedy; a *future* `schema_version` |
| 22 | + exits cleanly with "upgrade tycoon-cli" instead of tracebacking. See |
| 23 | + the [`schema_version` reference](../reference/tycoon-yml.md#schema_version). |
| 24 | +- **Config singleton on its way out** (#94, PR #190) — the ingestion |
| 25 | + commands (`sources`, `run-all`, `sync`, `explore`) construct their |
| 26 | + config at invocation through a `load_config()` factory rather than an |
| 27 | + import-time singleton, which is what keeps `--help` and |
| 28 | + `init --upgrade` safe in front of any project file. The remaining |
| 29 | + singleton users are tracked in #175, broader enforcement coverage |
| 30 | + in #189. |
| 31 | +- **CI that can't drift** (PR #174) — ruff pinned (CI previously ran |
| 32 | + whatever `uvx ruff` resolved to, so upstream releases broke builds), |
| 33 | + `ruff format --check` gating every PR, and a one-time repo-wide |
| 34 | + format pass. |
| 35 | + |
| 36 | +## Upgrading from 0.1.10 |
| 37 | + |
| 38 | +- **Existing projects keep working.** The first data command prints a |
| 39 | + one-time-per-invocation warning that `tycoon.yml` is at an older |
| 40 | + schema version; run `tycoon init --upgrade` in the project directory |
| 41 | + to migrate. The migration adds a `metadata:` block with defaults and |
| 42 | + stamps `schema_version: 2` — nothing else in your file is touched. |
| 43 | +- **No command or flag was removed.** New runtime dependency |
| 44 | + `ruamel-yaml` installs automatically with the package. |
| 45 | +- **Dependency floors moved** (PR #180): `dbt-core` 1.12.0 and `typer` |
| 46 | + 0.27.0. dbt-core 1.12 pulls metricflow into the tree; if you pin |
| 47 | + tycoon's dependencies downstream, re-lock. |
| 48 | + |
| 49 | +## Behind the scenes |
| 50 | + |
| 51 | +- The T2-4 review round produced four follow-ups (#185–#188), all |
| 52 | + closed in this release: template scaffolding no longer flattens |
| 53 | + `tycoon.yml` formatting, a dead conditional in `save_project` is |
| 54 | + gone, the schema surface is documented, and a subprocess-layer test |
| 55 | + now guards the "hostile tycoon.yml bricks the CLI at import time" |
| 56 | + regression class that in-process tests can't see. |
| 57 | +- Dependabot's per-bump PRs are replaced by a release-time dependency |
| 58 | + review (PR #180 is the first) — runtime pins and SHA-pinned actions |
| 59 | + reviewed in one pass, dev-only noise dropped. |
| 60 | + |
| 61 | +## What's next |
| 62 | + |
| 63 | +Milestone 3 of the ingestion rewrite — the verified-source catalog |
| 64 | +(manifest, `SourceSpec` models, spec-driven config collection) — is |
| 65 | +already in flight on the `v0.1.12` branch. Remaining schema-enforcement |
| 66 | +coverage (#189) and the rest of the singleton removal (#175) ride with |
| 67 | +it. See the [ingestion architecture doc](../ingestion-architecture.md) |
| 68 | +and #81 for the sequence. |
0 commit comments