Repository navigation
chore(release): v0.12.12 #1798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore(release): v0.12.12 #1798
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,62 @@ All notable changes to this project will be documented in this file. | |
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), | ||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
|
||
| ## [0.12.12] - 2026-11-20 | ||
|
|
||
| **dbt Power User features now work from the command line, and an owner can send a workspace request back for changes.** Nine new tools estimate what a dbt model or query would scan before it runs (BigQuery dry run, Snowflake and Databricks from the planner's EXPLAIN), read the last dbt run, check a model's docs coverage, report DataPilot project health, time a model's CTEs, draw its SQL graph, map raw SQL tables to `ref()` and `source()`, read the defer setting, and reply to comments on shared dbt docs. Call them with `altimate-code tool run` or from another coding agent through `mcp serve`. The new `altimate-code integrations` command connects GitHub, Jira and Linear with your own credentials. On workspaces with review on, a request can be sent back with a comment, then changed and sent again. The TUI says what changed in the workspace's skills and knowledge since your last session. Also in this release: stricter SQL checks in the tool CLI and MCP server, the agent keeps your changes instead of reverting them, `altimate review` reviews only the PR's own changes, and Snowflake key-pair login reads every private-key format. | ||
|
|
||
| **Heads-up for support:** | ||
| - **The dbt Power User tools are not offered to the agent in the TUI.** They are in `altimate-code tool run` and `mcp serve` only. `dbt_cost_estimate`, `dbt_health`, `dbt_cte_profile` (when timing a CTE) and `dbt_sql_graph` start the project's dbt adapter, which runs `dbt deps` and renders Jinja, so they need `--allow-write` and refuse in plan mode. `dbt_health` also needs the `altimate-datapilot-cli` package in the project's Python. | ||
| - **What `dbt_cost_estimate` runs.** It never runs the query itself. On Databricks, `EXPLAIN COST` can start a stopped SQL warehouse, which is billed while it runs. Snowflake's number is an upper bound, except when the plan reads an external table, a stage or a secure view, or reports 0, which the answer says. A query that may hold a second statement, or that reads files on Databricks (including through `IDENTIFIER()`), gets no estimate. An EXPLAIN that takes over 90 s answers "explain failed". `dbt_cte_profile` runs one `COUNT(*)` per CTE timed. | ||
| - **The tool CLI and MCP server refuse more SQL, even with `--allow-write`.** The new refusals are `DROP CATALOG`, `DROP NAMESPACE`, `DROP EXTERNAL SCHEMA`, `DROP PLUGGABLE DATABASE`, and MySQL and MariaDB executable comments (`/*! ... */`). Jinja in SQL sent to a dbt target counts as a write. `sql_explain` explains one statement only, without leading `EXPLAIN` or its options. | ||
| - **On Snowflake, MySQL and ClickHouse, a backslash inside a quoted string makes the SQL uncertain.** `sql_explain` refuses it and says so, and `sql_execute` treats it as a write. Regexes and Windows paths are the usual triggers. Tracked in #1782. | ||
| - **`altimate integrations` keeps secrets in the macOS keychain on macOS.** On Linux and Windows they are kept in a file in the data directory. Tracked in #1785. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: Document that setting Prompt for AI agents |
||
| - **The tools that start the dbt adapter no longer write to the project's `target/`.** In the `core` and `corecommand` modes dbt writes their artifacts to `<target-path>/.altimate-code/`, so `target/manifest.json` stays as your own `dbt compile` left it. The first such call on a project parses it in full, so it is slower once. The `fusion` and `cloud` modes still write to `target/`. | ||
| - **`altimate review` in CI now fails when the PR's target branch isn't fetched**, instead of guessing `origin/main`. Use `fetch-depth: 0`. `--base` with no common history also fails. | ||
| - **New integration surfaces for plugins.** `skill publish --json` refusals carry a `code`. Requests can have the status `changes requested`. `serve` adds `POST /altimate/rules/{id}/withdraw|resubmit` `GET /altimate/workspace/activity` and `POST /altimate/workspace/activity/seen`. | ||
|
|
||
| ### Added | ||
|
|
||
| - **`dbt_cost_estimate`** — the bytes a dbt model or query would scan, without running it: a BigQuery dry run, Snowflake `EXPLAIN USING JSON` and Databricks `EXPLAIN COST`. (#1732, #1768, #1776, #1779) | ||
| - **`dbt_run_results`** — the last dbt run's invocation id, command, timings, counts and per-node results, failures first. (#1729) | ||
| - **`dbt_docs_coverage`** — which output columns of a model have no description, and the percent documented. Column reach keeps how each reached column comes from the traced one. (#1733) | ||
| - **`dbt_health`** — DataPilot project health insights per model, such as hard-coded references and missing tests or docs. (#1738) | ||
| - **`dbt_cte_profile`** — a model's CTEs in source order, or the row count and warehouse time of one CTE, without dbt's start-up. (#1731, #1781) | ||
| - **`dbt_sql_graph`** — a model's CTEs, joins and filters as a graph, with joins, filters, groups and sorts named by their clause. (#1735, #1781) | ||
| - **`dbt_map_relations`** — the `ref()` or `source()` call for each table in raw SQL, matched against the manifest. (#1737) | ||
| - **`dbt_defer_state`** — the dbt Power User defer setting and the profile's targets. (#1734) | ||
| - **`docs_share_comments`** — list, reply to and resolve comment threads on shared dbt docs. (#1730) | ||
| - **`altimate-code integrations`** — connect GitHub, Jira and Linear with your own credentials: `status`, `detect`, `fields`, `set`, `set-secret`, `connect`, `sync`, `block` and `disconnect`. Secrets never go on the command line, and a credential stays local or is saved to the workspace. See "Integrations" in the CLI docs. (#1622) | ||
| - **Request changes on workspace review.** The owner or an admin can send a skill, knowledge or rule request back with a comment. You are told once, `workspace review status` and `/rules` show the comment, and the request can be sent again or withdrawn. Claude Code and Codex sessions are told too. (#1755) | ||
| - **"What changed" in a linked workspace.** A few seconds after the TUI starts, one line names the skills and knowledge added or removed since your last session. The VS Code extension gets the same line from `serve`. (#1752) | ||
| - **The Claude Code plugin's dbt helpers** are documented in "Using with Claude Code", including what `altimate-dbt` is. (#1728, #1779) | ||
| - **`tool report-event` takes the Claude Code plugin's session-start and feature-used events**: versions, the OS and a random install id, with no session, machine, project or account id, and skipped when telemetry is off. (#1775) | ||
|
|
||
| ### Changed | ||
|
|
||
| - **Stricter SQL classification in the tool CLI and MCP server** (see Heads-up). (#1644) | ||
| - **`altimate review` reviews only the PR's own changes.** The base comes from `--base` or the CI target branch, the diff is taken from the merge-base, only files in the dbt project are reviewed, renamed models keep their old side, custom `model-paths` are honoured, and a Jinja model without compiled SQL is marked unverified instead of getting warnings. (#1719) | ||
| - **The agent keeps your changes.** When a test or build fails because of a change you made, it fixes the test or the callers, or asks, instead of reverting your change. It never weakens a test to make it pass. (#1766) | ||
|
|
||
| ### Fixed | ||
|
|
||
| - **A link that hits a workspace you cannot see names the workspace id and the account you are signed in as.** Before, it said only "a workspace you can't see". (#1764) | ||
| - **Workspace review decisions are no longer hidden by "Sync now".** Decisions that arrive together show as one toast. (#1751) | ||
| - **The column answer reads a cast after a SELECT modifier or in parentheses**, and column names at the edges of the answer are right. (#1760, #1754) | ||
| - **`schema-verify` says when its verdict rests on a stale manifest.** (#1704) | ||
| - **Snowflake key-pair login reads every private-key format**: PEMs whose line breaks became spaces, encrypted PKCS#8 keys without a passphrase, and legacy encrypted PKCS#1 keys. (#1777) | ||
| - **`serve` never sends a stack trace in an error response.** A remote config that can't be fetched is a 502 that names the remote. (#1788) | ||
| - **A missing npm on Windows is reported as missing**, not as a failed driver install. (#1790) | ||
| - **dbt tool argument errors name the field**, and activating a different virtualenv (`VIRTUAL_ENV`, `CONDA_PREFIX`) gets a `tool run` daemon that uses it. (#1781) | ||
| - **Release review fixes.** | ||
| - `integrations connect` names the next step when fields are missing. | ||
| - The `ALTIMATE_INTEGRATIONS_*_API` overrides must be https or a local address. | ||
| - The dbt adapter refusal names plan mode. | ||
| - `dbt_run_results` accepts a UNC target path and skips a `run_results.json` over 256 MiB. | ||
| - The dbt Power User tools and `integrations` are documented. | ||
| - `altimate review` refuses a `--base` or `--head` that starts with `-`. | ||
| - Remote-config errors and the debug log name the remote by its URL template, never the URL with the token filled in. | ||
|
|
||
| ## [0.12.11] - 2026-11-16 | ||
|
|
||
| **You can use a Claude Pro or Max plan through your own Claude Code login, and workspace review works from every client.** The new Claude subscription provider runs Claude models through the `claude` you already have installed; Altimate Code never reads or stores its token. The first-run picker and `/connect` suggest the subscription logins already on the machine. On workspaces with review on, a member's skill goes to the owner or an admin for approval, everyone sees their own requests and their status, and requests can be withdrawn or removed from the TUI, `serve` and the plugins. Team rules also reach Claude Code and Codex sessions through the plugins. `impact_analysis` answers where a column's value goes, or where it comes from, hop by hop. Also in this release: a capped agent ends with an answer, one overflow compacts once, and the dbt adapter starts under Bun. | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,6 +1,6 @@ | ||||||
| --- | ||||||
| title: "dbt Tools — Altimate Code" | ||||||
| description: "Run dbt commands from Altimate Code using the dbt_run tool with full output capture and error reporting." | ||||||
| description: "dbt tools in Altimate Code: dbt_run, dbt_manifest, dbt_unit_test_gen, and the dbt Power User tools for cost estimates, run results, docs coverage, project health, CTE timing, SQL graphs, relation mapping, defer state and shared-docs comments." | ||||||
| --- | ||||||
|
|
||||||
| # dbt Tools | ||||||
|
|
@@ -140,6 +140,43 @@ unit_tests: | |||||
|
|
||||||
| --- | ||||||
|
|
||||||
| ## dbt Power User tools | ||||||
|
|
||||||
| These tools bring dbt Power User features to the command line. Call them with `altimate-code tool run <id> --args '<json>'` (see [Tool CLI](../../usage/tool.md)) or from another coding agent through `altimate-code mcp serve`. The agent in the TUI does not offer them. | ||||||
|
|
||||||
| Some of them start the project's dbt integration (the dbt adapter), which runs `dbt deps` and renders the project's Jinja. Jinja `run_query` calls can run billed queries. A read-only call (`altimate-code tool run` without `--allow-write`, or plan mode) does not start the adapter, so these tools refuse it. | ||||||
|
|
||||||
| ### Tools that start the dbt adapter and so need `--allow-write` | ||||||
|
|
||||||
| | Tool | What it returns | Parameters | What it runs on the warehouse | | ||||||
| | --- | --- | --- | --- | | ||||||
| | `dbt_cost_estimate` | The bytes a model or a query would scan, without running it. | `model` or `sql` (may use Jinja), not both | BigQuery: a dry run. Snowflake: `EXPLAIN USING JSON`, bytes left after pruning, an upper bound. Databricks: `EXPLAIN COST`, the sizes of the tables it reads, which can start a stopped SQL warehouse (billed while it runs). A query that may hold a second statement, or that reads files on Databricks, is refused rather than planned. | | ||||||
| | `dbt_health` | DataPilot project health insights per model, such as hard-coded references, missing tests or documentation, and naming and structure issues. | `config_path` (optional DataPilot config) | Nothing. It needs the `altimate-datapilot-cli` Python package in the project's Python. | | ||||||
| | `dbt_cte_profile` | Without `cte` or `position`: the model's CTEs in source order. With one: that CTE's row count and its warehouse time in milliseconds (`queryMs`, without dbt's start-up; `timing` says how it was measured). | `model` (name, unique_id or `.sql` path), `cte`, `position` | Listing runs nothing and works read-only. Timing runs `SELECT COUNT(*)` over that CTE and the CTEs before it, so a model of N CTEs costs N queries. | | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Document the wall-time fallback. If dbt timing and the baseline are unavailable,
|
||||||
| | `dbt_cte_profile` | Without `cte` or `position`: the model's CTEs in source order. With one: that CTE's row count and its warehouse time in milliseconds (`queryMs`, without dbt's start-up; `timing` says how it was measured). | `model` (name, unique_id or `.sql` path), `cte`, `position` | Listing runs nothing and works read-only. Timing runs `SELECT COUNT(*)` over that CTE and the CTEs before it, so a model of N CTEs costs N queries. | | |
| | `dbt_cte_profile` | Without `cte` or `position`: the model's CTEs in source order. With one: that CTE's row count and its warehouse time in milliseconds (`queryMs`; `timing` says how it was measured). `queryMs` excludes dbt start-up for `dbt` and `baseline` timing, but includes it for `wall`. | `model` (name, unique_id or `.sql` path), `cte`, `position` | Listing runs nothing and works read-only. Timing runs `SELECT COUNT(*)` over that CTE and the CTEs before it, so a model of N CTEs costs N queries. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: dbt_sql_graph reads parent-relation column metadata from the warehouse via getBulkSchemaFromDB; it is not warehouse-free. Document that metadata access in this column.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At docs/docs/data-engineering/tools/dbt-tools.md, line 156:
<comment>`dbt_sql_graph` reads parent-relation column metadata from the warehouse via `getBulkSchemaFromDB`; it is not warehouse-free. Document that metadata access in this column.</comment>
<file context>
@@ -140,6 +140,43 @@ unit_tests:
+| `dbt_cost_estimate` | The bytes a model or a query would scan, without running it. | `model` or `sql` (may use Jinja), not both | BigQuery: a dry run. Snowflake: `EXPLAIN USING JSON`, bytes left after pruning, an upper bound. Databricks: `EXPLAIN COST`, the sizes of the tables it reads, which can start a stopped SQL warehouse (billed while it runs). A query that may hold a second statement, or that reads files on Databricks, is refused rather than planned. |
+| `dbt_health` | DataPilot project health insights per model, such as hard-coded references, missing tests or documentation, and naming and structure issues. | `config_path` (optional DataPilot config) | Nothing. It needs the `altimate-datapilot-cli` Python package in the project's Python. |
+| `dbt_cte_profile` | Without `cte` or `position`: the model's CTEs in source order. With one: that CTE's row count and its warehouse time in milliseconds (`queryMs`, without dbt's start-up; `timing` says how it was measured). | `model` (name, unique_id or `.sql` path), `cte`, `position` | Listing runs nothing and works read-only. Timing runs `SELECT COUNT(*)` over that CTE and the CTEs before it, so a model of N CTEs costs N queries. |
+| `dbt_sql_graph` | A model's CTEs, joins and filters as a graph, each relation tied to the dbt node it stands for. | `model` | Nothing. |
+
+### Read-only tools
</file context>
| | `dbt_sql_graph` | A model's CTEs, joins and filters as a graph, each relation tied to the dbt node it stands for. | `model` | Nothing. | | |
| | `dbt_sql_graph` | A model's CTEs, joins and filters as a graph, each relation tied to the dbt node it stands for. | `model` | Reads parent-relation column metadata from the warehouse when applicable. | |
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -29,6 +29,7 @@ altimate --agent analyst | |||||
| | `run` | Run a prompt non-interactively | | ||||||
| | `check` | Run deterministic SQL checks (no LLM required) -- see [SQL Check](check.md) | | ||||||
| | `tool` | Run the data tools without a model, optionally via a warm daemon -- see [Tool CLI](tool.md) | | ||||||
| | `integrations` | Connect GitHub, Jira and Linear with your own credentials -- see [Integrations](#integrations) | | ||||||
| | `serve` | Start the HTTP API server | | ||||||
| | `web` | Start the web UI | | ||||||
| | `agent` | Agent management | | ||||||
|
|
@@ -75,6 +76,24 @@ With workspaces on: | |||||
| - When `altimate-code serve` is launched by the VS Code / Cursor extension, the workspace selected in the extension's panel governs that session's skills, memory and (unless `--integrations local` is set) warehouse tool routing, taking priority over whatever the project is linked to on the backend, and is scoped to the folder it was launched for. A pin is fixed for the life of the `serve` process, so the extension relaunches `serve` when the selection changes; nothing updates a running one. | ||||||
| - `serve` also gives the IDE extension what the TUI shows: `GET /altimate/workspace/starter` (the starter message after a link) and `GET /altimate/trace` with `GET /altimate/trace/<session>/view` (the trace list and viewer behind `/traces`). Traces hold prompts and tool output, including SQL and query results. Like every `serve` route, these need no password unless `OPENCODE_SERVER_PASSWORD` is set, so set one on a shared machine. | ||||||
|
|
||||||
| ### Integrations | ||||||
|
|
||||||
| `altimate-code integrations` connects GitHub, Jira (Cloud or Server / Data Center) and Linear with your own credentials. A credential can stay on this machine or be saved to the linked workspace. Every subcommand accepts `--json`. | ||||||
|
|
||||||
| ```bash | ||||||
| altimate-code integrations status # each provider's state | ||||||
| altimate-code integrations detect # find credentials already on this machine (secrets are never printed) | ||||||
| altimate-code integrations fields jira # the fields a provider needs, pre-filled where possible | ||||||
| altimate-code integrations set jira jiraDomain mycompany | ||||||
| altimate-code integrations set-secret jira jiraApiToken --from-clipboard | ||||||
| altimate-code integrations connect jira # check the credential with the provider, then save it | ||||||
| ``` | ||||||
|
|
||||||
| - `set-secret` reads a secret only from `--from-clipboard`, `--from-env <VAR>` or `--stdin`, never from the command line. `open-token-page <provider>` opens the page where the provider's token is created. | ||||||
| - `connect` checks the credential with the provider before saving it. With `--local-only` it stays on this machine. Otherwise it is saved to the linked workspace. Attaching it to a workspace that is not private, so its members can use it, needs `--share`. | ||||||
| - `update <provider>` saves a new credential and keeps the sync mode. `sync [provider] | --all` pushes credentials to the workspace. `block` and `unblock` keep a provider on this machine only or allow it to sync again. `discard` forgets fields typed in but not connected. `disconnect` removes the local credential and the workspace connection. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: Prompt for AI agents
Suggested change
|
||||||
| - On macOS, secrets are kept in the keychain. On Linux and Windows they are kept in a file in your altimate-code data directory, readable only by you on Linux (mode 0600). Windows does not apply that mode. | ||||||
|
|
||||||
| ## Global Flags | ||||||
|
|
||||||
| | Flag | Description | | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -604,9 +604,14 @@ export interface Validation { | |
| message: string | null | ||
| } | ||
|
|
||
| const githubApi = () => (process.env.ALTIMATE_INTEGRATIONS_GITHUB_API || "https://api.github.com").replace(/\/+$/, "") | ||
| const linearApi = () => process.env.ALTIMATE_INTEGRATIONS_LINEAR_API || "https://api.linear.app/graphql" | ||
| const jiraCloudBase = (site: string) => (process.env.ALTIMATE_INTEGRATIONS_JIRA_API || `https://${site}.atlassian.net`).replace(/\/+$/, "") | ||
| // An override receives the real token, so it must be https or a local http address, as a Jira server URL must; any other value is ignored. | ||
| const apiOverride = (name: string) => { | ||
| const v = process.env[name] | ||
| return v && (/^https:\/\//i.test(v) || /^http:\/\/(127\.0\.0\.1|localhost)(:|\/|$)/i.test(v)) ? v : undefined | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. WARNING: The "https or a local http address" gate is decided by a prefix regex, not the parsed host, so it accepts URLs whose real host is remote.
Parse instead: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reject override URLs that carry credentials or name a nonlocal host. The check at line 610 matches the raw string by prefix. It does not parse the URL. An override such as Parse the value with
|
||
| } | ||
| const githubApi = () => (apiOverride("ALTIMATE_INTEGRATIONS_GITHUB_API") || "https://api.github.com").replace(/\/+$/, "") | ||
| const linearApi = () => apiOverride("ALTIMATE_INTEGRATIONS_LINEAR_API") || "https://api.linear.app/graphql" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P1: The https-only check stops plaintext transport, but it does not stop redirection. Any https host is accepted, so a credential detected from the environment can be sent to a host the environment names. Restrict the override to known hosts, or check the destination host as the GitHub guard does. Prompt for AI agents |
||
| const jiraCloudBase = (site: string) => (apiOverride("ALTIMATE_INTEGRATIONS_JIRA_API") || `https://${site}.atlassian.net`).replace(/\/+$/, "") | ||
|
|
||
| /** GitHub sends the expiry as `2026-11-01 00:00:00 UTC`. */ | ||
| export function parseGithubExpiry(header: string | null): string | null { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document the macOS file-storage exception.
When
ALTIMATE_INTEGRATIONS_DIRis set on macOS,useKeychain()returns false and secrets are written tointegrations-secrets.json. This contradicts the unconditional keychain guarantee. State this exception here and in the storage note indocs/docs/usage/cli.md. Users need an accurate description of where plaintext credentials can remain. (raw.githubusercontent.com)