chore(release): v0.12.8

Merged
SA
19h ago
+1630-22

Issue for this PR

Release PR. Closes #1580, closes #1583, closes #1585. Partly addresses #1578 (env var only) and #1581 (tests for two of the four modules).

It promotes the v0.12.7..main payload to latest as v0.12.8: #1552, #1562, #1570, #1567, #1553, #1559, #1556, #1561, #1471, #1462, #1461, #1555, #1548, #1544, #1542, #1541, #1448, #1446, #1480, #1536, #1534, #1532, #1528, #1530, #1441, #1524, #1517, #1514, #1445, #1450, #1258, #1472, #1470, #1469, #1429, #1464, #1431.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation
  • Other: release

What does this PR do?

Nine commits on top of main (639029d778):

  • release: v0.12.8: the CHANGELOG entry and this release's adversarial tests (test/skill/release-v0.12.8-adversarial.test.ts, 114 tests). The entry opens with a heads-up for support: the 3 s socket-stdin wait in run, the unsent-memory line, unquoted run prompts, policy and semantic checks failing closed on altimate-core 0.9.0, schema_inspect sending sampled values to the model provider, the masked error_message in telemetry, deny rules matching equivalent paths, per-project warehouse connections, and datamate_manager being off in linked projects.
  • fix: release review follow-ups for v0.12.8: the run stdin timeout notice says later input is ignored; uninstall on Windows says its commands are for PowerShell; the error_message type comment describes the shipped fixed-vocabulary mask; docs for the fail-closed checks, schema_inspect value profiles, client_connected, /integrations, datamate_manager in linked projects, the run quoting change, and the Windows .cmd shim.
  • fix(check): tell the user to review a statement policy cannot evaluate (#1585): the policy_not_evaluated and skipped-semantics messages name the constructs and say to review by hand.
  • feat(schema_inspect): ALTIMATE_DISABLE_SCHEMA_VALUES turns value profiles off (#1578): no sample query runs when it is set, whatever the model passes, and the output says so. A per-warehouse setting would need new config and is left open.
  • fix(storage): say why startup waits on the first-run setup lock (#1580): after 5 s waiting on another process's <db>.setup-lock, one stderr line names the lock; the 60 s limit is unchanged.
  • fix(sql): treat replication-slot copy and sync functions as side effects (found by Cubic on this PR): pg_copy_logical_replication_slot, pg_copy_physical_replication_slot and pg_sync_replication_slots passed the read-only check as top-level calls; the create and drop slot functions were already denied.
  • fix: release PR review follow-ups and test: move the policy skip-guard case: the consensus review of this PR (5 models, approve, no critical or major) and the bot comments: PowerShell command for the .opencode directory on Windows, a failing lock notice can no longer abort the database open, deterministic setup-lock tests, accurate schema_inspect and check docs, and the CHANGELOG lock-notice wording. Deferred: #1588.
  • test: Windows shim parity between install and install.ps1 (#1583), and direct tests for sql-function-policy and schema/index-control (#1581).

Release review: five reviewers (CTO, product, data engineer, tech lead, and a support engineer on the Monday after release) all said ship with notes, with no P0 and no HOLD. Deferred findings are filed: #1577, #1579, #1581 (rest), #1582, #1586. #1584 was closed: the installers' install directory is fixed, so the case cannot occur.

After merge: tag the merge commit v0.12.8 and push only the tag, which starts release.yml.

How did you verify your code works?

  • Preflight --stage pre and --stage tag passed (9/9 each). Typecheck and marker guard are clean.
  • Full opencode suite: 19,758 passed, 9 failed, all explained:
    • 6 MCP tests read the developer's own MCP config and pass with an isolated HOME (14/14).
    • 2 are the --time-budget JSON-output tests that also fail on main.
    • 1 v2 pty test times out under full-suite load and passes alone (4/4).
  • Adversarial tests 114/114. Fix-specific suites: install 295/295, schema_inspect 88/88, setup lock 27/27, SQL function policy and index control 106/106, policy fail-closed and check e2e 101/101, per-project registry and SSH tunnels 34/34.
  • pre-release passed and the darwin-arm64 binary reports 0.12.8; --help and workspace --help list the new commands.
  • Verdaccio sanity suite, local Docker, linux-arm64 build of 0.12.8: all phases passed, 68 passed, 0 failed, 10 skipped (the same totals as v0.12.7). Phases: installation 13/13, extended installation 22/22, smoke 0 (1 skipped), resilience 3 (8 skipped), extended resilience 14 (1 skipped), security 16/16.

Cost side effects

None added by the release commits. schema_inspect value profiles (#1542) run one bounded query per table (10,000-row sample, 40 columns, 15 s timeout; 100 documents on MongoDB); ALTIMATE_DISABLE_SCHEMA_VALUES turns them off.

Screenshots / recordings

N/A

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR
  • I checked for cost side effects (model calls, queries or cloud resources that grow with user data) and described them, or wrote "none"

🤖 Generated with Claude Code

https://claude.ai/code/session_011chv9Rmu7jQXokum1WNcs7

Summary by CodeRabbit

  • New Features

    • Schema inspection can display column value profiles; profiles can be disabled per request or through an environment setting.
    • The CLI documents workspace integration status and managed integration behavior.

  • Improvements

    • Policy checks treat statements they cannot evaluate as blocked; semantic checks report a finding.
    • Run guidance clarifies stdin timeouts and argument quoting. Late stdin is ignored after a timeout.
    • Database setup waits can display a notice, and uninstall instructions provide platform-specific commands.

  • Documentation

    • Updated guidance covers schema profiles, telemetry, Windows command aliases, and CLI usage.