Skip to content

sdk: release 0.2.23 - #367

Merged
foxnne merged 1 commit into
mainfrom
sdk/release-0.2.23
Oct 11, 2026
Merged

foxnne merged 1 commit into
mainfrom
sdk/release-0.2.23

Conversation

@foxnne

@foxnne foxnne commented Oct 10, 2026

Copy link
Copy Markdown
Collaborator

What changes

sdk_version goes from 0.2.22 to 0.2.23. Merging tags sdk-v0.2.23, publishes its tarball, and asks the store plugins to repin.

Why now. The plugin boundary's fingerprint moved since sdk-v0.2.22 (0x1bf417f6… → 0x65096e94…, by #360), so store plugins built against 0.2.22 don't load in a fizzy built from main, and fizzyed.it/app is built from main. Also, #355 moved the plugins service to version 2, and the agent plugin's fizzy_build asks for version 1 until it repins.

SDK impact

  • None
  • Core-only or additive: reaches plugins at the next SDK release
  • Fingerprint moved: recorded in sdk/src/version.zig, sdk_version untouched, PR labelled sdk
  • SDK release: bumps sdk_version, lists the sdk PRs since the last sdk-v* tag

The sdk PRs since sdk-v0.2.22:

Additive, reaching plugins with this release:

Also reaching plugins (core/):

Verified

  • macOS:
    • zig build and test-sdk-version on this head.
    • scripts/pack-sdk.sh packs fizzy-sdk-v0.2.23.tar.gz.
    • Every store plugin (fresh pulls of pixi, zig, drive, atlas and ghostty main) builds against this tree's sdk/ with zig build --fork=<sdk> into a throwaway profile (31/31, and 28/28 for each of the other four). The fingerprint moved, so each repin PR is a real rebuild, but none should open as a draft for a broken build. The agent and chat plugins build too (22/22, 19/19).
  • Windows:
  • Linux: CI.
  • Web:

Follow-ups

  • Each repin PR merged and its plugin tagged (the plugin repos' tags stay the maintainer's).
  • fizzyedit/agent and fizzyedit/chat repin to the sdk-v0.2.23 tarball.

🤖 Generated with Claude Code

@foxnne
foxnne merged commit cc9886f into main Oct 11, 2026
10 checks passed
@foxnne
foxnne deleted the sdk/release-0.2.23 branch October 11, 2026 00:02
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