The version job ran `bunx changeset version` to consume .changeset/*.md
files and update CHANGELOG.md, but the publish job (which commits and
pushes) ran on a separate runner with a fresh checkout — discarding all
changelog changes. This caused CHANGELOG.md to stay stuck at 7.2.1
despite 9 subsequent releases.
Move changeset consumption into publish.ts so it runs on the same runner
that commits. Extract release notes from the updated changelog and pass
them to `gh release edit` so GitHub releases also get correct notes.
Remove standalone changeset-release.yml workflow (version bump PR approach).
Instead, run changeset version inside publish.yml's version job to consume
.changeset/*.md files into CHANGELOG.md, then extract the latest section
for GitHub release notes. This replaces the previous AI-generated changelog
(opencode run --command changelog) with changeset-based entries.
* tweak: use theme tokens for debug bar surface
* chore: update nix node_modules hashes
* feat(tui): add heap snapshot functionality for TUI and server (#19028)
* ci
* change model for changelog
* release: v1.3.2
* refactor: kilo compat for v1.3.2
---------
Co-authored-by: Jay V <air@live.ca>
Co-authored-by: opencode-agent[bot] <opencode-agent[bot]@users.noreply.github.com>
Co-authored-by: Dax <mail@thdxr.com>
Co-authored-by: Dax Raad <d@ironbay.co>
Co-authored-by: opencode <opencode@sst.dev>
Co-authored-by: Imanol Maiztegui <imanol.mzd@gmail.com>
When the publish workflow is dispatched with pre_release=true, the CLI
and SDK packages are now published to npm under the "rc" dist-tag with
a semver prerelease version (e.g. 7.1.24-rc.202604081425) instead of
going to the "latest" tag as a stable release.
This ensures that pre-release VS Code extension builds ship with a
matching pre-release CLI on npm, so users on the stable channel are
never affected by pre-release publishes.
kiloconnect[bot]