Files
gpuix/.changeset
Tommy D. Rossi 7ac9880abd release: @gpuix/native@0.9.0 and @gpuix/react@0.9.0
Consume the pending changesets into a minor release. Users get a window-level onSelectionChange callback for text selection, a live-window click panic fix, and docs to pin @gpuix/react and @gpuix/native to the same exact version.

Bump the native Cargo crate, native npm package, React package, generated napi loader version checks, and Bun workspace lock to 0.9.0. Keep the published React dependency on @gpuix/native as workspace:^. CI is the only publish path for native platform binaries.

Fixes #38

Session: ses_f56207a65ffeFBg1JxfiwGIPqH
2026-09-16 13:07:10 +02:00
..
2026-08-19 20:55:43 +02:00

Changesets

This folder contains pending release notes for @gpuix/native and @gpuix/react. Each .md file describes one user-facing fix or feature that should appear in the next generated changelog.

What to put here

  • Add one descriptive kebab-case .md file per logical change, for example fix-frame-loop-cpu.md.
  • Use patch for fixes and minor for new features.
  • Write in present tense, focused on what users see.
  • Check GitHub issues first. If the change fixes one, include Fixes #123 on its own line.

What not to put here

  • Do not add changesets for private packages or packages without a version field.
  • Do not edit CHANGELOG.md directly.
  • Do not run the interactive changeset CLI.
  • Do not add vague entries like "misc improvements" or "update internals".