chore(release): v0.12.2-beta.1

Merged
SA
2mo ago
+15-0

Issue for this PR

Release PR ā€” no issue. Beta of the six fixes merged after v0.12.1: #1341, #1342, #1343, #1344, #1345, #1346.

Type of change

  • Other: release

What does this PR do?

Adds the ## [0.12.2-beta.1] CHANGELOG entry. Once merged, the merge commit is tagged v0.12.2-beta.1; the -beta.1 suffix routes the release workflow to the npm beta dist-tag, so latest (0.12.1) is untouched and nobody is auto-upgraded. The changelog is baked into the binary and every npm package at build time, so it has to be in the tagged commit.

How did you verify your code works?

Local gates on this commit (the release workflow's own, reproduced before tagging):

  • bun script/release-preflight.ts --version 0.12.2-beta.1 --stage pre --allow-prerelease: PASS (tag free locally and remotely; notes diff against v0.12.1; no prerelease tags on the 0.12 line; no release-blocker PRs; marker guard clean)
  • bun turbo typecheck --force: 13/13 packages
  • OPENCODE_VERSION=0.12.2-beta.1 bun run pre-release: PASS ā€” the dist binary starts and reports 0.12.2-beta.1
  • Package size: 173 MB compressed (npm limit ā‰ˆ190)
  • Verdaccio install sanity (Docker, linux-arm64 build): running; result posted here before merge

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

šŸ¤– Generated with Claude Code

https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6

Summary by cubic

Prepares the v0.12.2-beta.1 release by adding its CHANGELOG entry, now with a corrected docs path. The release publishes to the npm beta dist-tag, so latest stays at 0.12.1 and no one is auto-upgraded; the changelog is baked into the binary and every npm package at build time, so it has to be in the tagged commit.

The six fixes it documents: environment variables are now read under their documented ALTIMATE_CLI_* names, /skills opens the Altimate skills browser, Snowflake metadata comparisons no longer misreport valid queries, team memory and one-shot run uploads survive, headless runs always end with an answer, and FinOps tools in linked projects route to the workspace engine.

Summary by CodeRabbit

  • Bug Fixes
    • Documented ALTIMATE_CLI_* environment variables now work consistently, including when multiple spellings are configured.
    • The /skills browser now provides clearer dialog actions, with installation assigned to the correct shortcut.
    • Snowflake validation no longer incorrectly reports correctly cased columns as missing.
    • Headless runs always return an answer or a clear failure status.
    • Linked-project FinOps tools now target the correct workspace engine and provide an explanatory error when unavailable.
    • Team memory reminders and synchronization now behave more reliably in supported pilot workflows.