chore(release): v0.12.12

SA
16m ago
+435-21

Issue for this PR

Closes #1797

Release PR. It promotes the v0.12.11..main payload (33 PRs) to latest as v0.12.12. Highlights: nine dbt Power User tools in tool run and mcp serve (#1729 to #1738, with #1768, #1776, #1779 and #1781); #1622 "feat: altimate integrations command"; #1755 request changes on workspace review; #1644 stricter SQL classification; and #1719 "fix(review): review the PR's own changes".

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds the 0.12.12 changelog entry, the release adversarial tests (packages/opencode/test/skill/release-v0.12.12-adversarial.test.ts, 37 cases), and the fixes from the release review.

Review fixes in this PR. They come from five persona reviews of the real diffs: one of the first 25 PRs, and a second of the 8 that landed on main after it. No P0, no HOLD on code.

  • integrations connect names the next step (fields, set, set-secret, connect) when fields are missing. (cli/cmd/integrations.ts)
  • ALTIMATE_INTEGRATIONS_*_API overrides are used only when they are https or a local http address, since they receive the real token. (altimate/integrations/credentials.ts)
  • The dbt adapter refusal says a read-only call doesn't start the adapter and names --allow-write and plan mode. (altimate/tools/dbt-adapter-access.ts)
  • dbt_run_results accepts a UNC target path and skips a run_results.json over 256 MiB. (altimate/validators/validator-utils.ts)
  • sql_explain says when a backslash in a quoted string is why it refuses, and how to write the string instead. (altimate/tools/sql-explain.ts)
  • altimate review refuses a --base or --head that starts with -, which git merge-base would read as an option. (altimate/review/git.ts)
  • Remote-config errors and the debug log name the remote by its URL template, not the URL with the token substituted. (config/config.ts)
  • Docs. A "dbt Power User tools" section in the dbt tools page (how to call them, which need --allow-write, what each runs on the warehouse), an "Integrations" section in the CLI page, and dbt_cte_profile's warehouse timing.
  • Tests. The tool CLI's tool list includes the nine new tools; the dbtAdapterFor Python-hint test runs with an empty HOME.

Deferred, with issues:

  • #1782 "Snowflake, MySQL and ClickHouse queries with a backslash in a quoted string are refused by sql_explain and treated as writes".
  • #1783 "one SQL tokenizer and shared helpers for the dbt Power User tools".
  • #1784 "dbt Power User tool edge cases (EXPLAIN errors, defer settings, run_results read race)".
  • #1785 "altimate integrations on Linux and Windows (plaintext secrets, jira-cli path, status legend)".
  • #1796 "dbt adapter refusal for a read-only target path, unchecked altimate-dbt doc examples, dbt_cost_estimate scanner".

How did you verify your code works?

  • Preflight: --stage pre passed on origin/main before the review; --stage tag on this branch gave 9 PASS, 0 WARN, 0 FAIL. The release notes will compare against v0.12.11.
  • Static checks: bun turbo typecheck passed on all 13 packages, and the marker guard is clean.
  • Release adversarial tests: 37 pass. They cover second-statement smuggling into dbt_cost_estimate on Snowflake and Databricks, hostile EXPLAIN JSON, the new hard-deny DROP forms, readRunResults against a directory, non-JSON, __proto__ and a 257 MiB sparse file, UNC and drive-letter target paths, the refusal messages, --base/--head refs starting with -, and source guards.
  • Full suite with an empty HOME: 22,859 pass, 11 fail. Nine (mask-file-paths, sample-setup) depend on the real home directory and pass when run with it. The other two are the --time-budget tests in json-output.test.ts, which CI never runs and which fail the same way on main; tracked in #1747.
  • Release binary smoke test: OPENCODE_VERSION=0.12.12 bun run pre-release reports "ALL CHECKS PASSED", both altimate and altimate-code report 0.12.12, tool run dbt_run_results answers, and review --base=-x is refused.

Cost side effects

None from the fixes in this PR. In the payload, dbt_cost_estimate on Databricks (#1768) runs EXPLAIN COST, which can start a stopped SQL warehouse; it is billed while it runs, and the docs and changelog say so. dbt_cte_profile runs one COUNT(*) per CTE it times.

Screenshots / recordings

n/a (CLI and docs).

🤖 Generated with Claude Code


Summary by cubic

Promotes the v0.12.11..main payload (33 PRs) to latest as v0.12.12: nine dbt Power User tools in tool run and mcp serve, the altimate-code integrations command, request-changes on workspace review, stricter SQL classification, and altimate review reviewing only the PR's own changes. Adds the 0.12.12 changelog entry, 37 release adversarial tests, and fixes from five persona reviews of the diff (no P0, no HOLD).

Release review fixes

  • integrations connect names the next step when fields are missing.
  • ALTIMATE_INTEGRATIONS_*_API overrides are honored only for https or local http, since they receive the real token.
  • The dbt adapter refusal names --allow-write and plan mode; sql_explain names a backslash as the cause of a refusal; dbt_run_results accepts UNC target paths and skips a run_results.json over 256 MiB.
  • altimate review refuses a --base/--head starting with -; remote-config errors and logs use the URL template, never the token-substituted URL.
  • Docs cover the dbt Power User tools and integrations; the tool CLI test asserts the nine tools.

Known issues are deferred: #1782, #1783, #1784, #1785, #1796.

Summary by CodeRabbit

  • New Features
    • Added CLI commands for connecting, updating, disconnecting, and syncing GitHub, Jira, and Linear integrations.
    • Expanded dbt Power User tools for warehouse operations, analysis, and shared documentation comments.
    • Added clearer guidance when integration credentials need additional fields.
  • Bug Fixes
    • Improved SQL classification messages, workspace review handling, and dbt tool access guidance.
    • Improved handling of Snowflake login errors, oversized run results, and invalid review references.
  • Documentation
    • Updated CLI and dbt tool guides with setup, permissions, and usage details.