Skip to content

docs: clarify Hex release note scope - #500

Merged
shuv1337 merged 1 commit into
integration-v2from
hex-notes
Nov 16, 2026
Merged

shuv1337 merged 1 commit into
integration-v2from
hex-notes

Conversation

@shuv1337

Copy link
Copy Markdown
Owner

Scope

Docs-only wording correction for the existing v2.3.0-shuv.3 release note. No app behavior change, no tip removal, no version, lockfile, workflow, generated file or test changes.

Change

CHANGELOG.md, the v2.3.0-shuv.3 App section, Hex bullet now reads:

The Hex item is a voice-input tip in the shared app/desktop source: it links to installing Hex and hides itself once Hex is installed. There is no Hex integration in the CLI/TUI, and no desktop binary ships in this release.

The same wording was applied in place to the existing GitHub release body with gh release edit --notes-file (notes only), as requested. The release was not republished and no workflow was dispatched; release ID, tag target, prerelease/draft flags, timestamps and all 23 assets are unchanged. npm dist-tags for shuvcode and shuvcode-node were identical before and after.

Source context (existing, unchanged): the tip is defined in packages/app/src/tips/model.ts and Hex install detection lives in packages/desktop/src/main/files/hex.ts. This PR only fixes the note's wording; it does not claim a fix for any issue.

Checks

  • Frozen install in a fresh isolated checkout from origin/integration-v2 at 61f0cb087d (1597 packages), then root bun run check: lint passed, typecheck 40/40 tasks, 0 cached, no type errors.
  • bun run prettier --ignore-unknown --check CHANGELOG.md: clean. git diff --check: clean.
  • No tests were run or modified; this is prose only.

With the docs: title the test workflow's unit/e2e jobs are skipped by the existing title guard, so I expect them to report SKIPPED rather than passed. Typecheck and the other always-on checks still run.

@shuv1337
shuv1337 merged commit d28ef32 into integration-v2 Nov 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant