Repository navigation
examples: replay-app moved to fizzyedit/example-app - #301
Merged
Merged
Conversation
With SDK 0.2.19 shipping `replay`, the replay app lives in fizzyedit/example-app (`zig build run-replay`) and fizzy's `examples/` is gone. `scripts/check-examples.sh` hands example-app's replay app this tree's SDK, packed as a release would be, and builds it, so CI still builds it against every pull request.
docs/AGENTS_PLAN.md and docs/AUTOMATION_PLAN.md moved to fizzyedit/plans (#296); their deletion stands here, and this branch's two edits to them go there (fizzyedit/plans#3). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
foxnne
marked this pull request as ready for review
October 10, 2026 01:12
foxnne
enabled auto-merge (squash)
October 10, 2026 01:12
foxnne
added a commit
that referenced
this pull request
Oct 10, 2026
## What changes `sdk_version` goes from 0.2.20 to 0.2.21. Merging tags `sdk-v0.2.21`, publishes its tarball, and asks the store plugins to repin. **Why now.** The plugin boundary's fingerprint moved since `sdk-v0.2.20` (`0x7b455e7a…` → `0x1bf417f6…`, by #331). Store plugins built against 0.2.20 do not load in a fizzy built from `main`, and fizzyed.it/app is built from `main`. The chat plugin (`fizzyedit/chat`) also needs #331's `Host.documentTitleChanged`, and builds against a local fork until this is out. ## 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` - [x] SDK release: bumps `sdk_version`, lists the `sdk` PRs since the last `sdk-v*` tag **The `sdk` PRs since `sdk-v0.2.20`:** - #331: a surface's title can change (`Host.setSurfaceTitle`, the Host keeping its own copy), and a document's tab follows its owner (`Host.documentTitleChanged`). `documentTitle`'s slice now need only last the call. **Also reaching plugins (`core/`, `sdk/replay`):** - #325: floats' screens are dvui's (`core/screens.zig`). - #326: `replay.overlay` draws through the backend's viewport picture. - #301: `sdk/replay_module.zig` follows `replay-app`'s move to fizzyedit/example-app. ## Verified - [x] macOS: - `zig build` and `test-sdk-version` on this head. - `scripts/pack-sdk.sh` packs `fizzy-sdk-v0.2.21.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>` (31/31 and 28/28 steps) into a throwaway profile. The fork matched, and the built plugin reports `pinned fizzy SDK: 0.2.21`. 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.21` tarball. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #281. Merge after fizzyedit/example-app#2: this PR's CI clones example-app's
mainand builds its replay app, which lands there in #2.What changes
examples/replay-appmoves to fizzyedit/example-app, aszig build run-replay, now that SDK 0.2.19 shipsreplay. Fizzy'sexamples/folder is gone.scripts/check-examples.shalso swaps example-app'sfizzy_sdkpin for this tree's SDK, packed as a release would be, and builds the replay app. So replay is still built against every pull request.examples/replay-appby path is gone.sdk/replay_module.zig,docs/AUTOMATION_PLAN.mdanddocs/AGENTS_PLAN.mdpoint at example-app's replay app.Not changed here:
scripts/plugin-loop/bench.pystill defaults toexamples/hello-plugin, which #282 removed. #292 is rewriting that script, so it is noted there rather than changed under it.SDK impact
sdk/replay_module.zig)Verified
scripts/check-examples.shagainst this tree and example-app with Ctrl/Cmd ambiguity per platform #2: example-plugin 28/28 steps; minimal, studio, endless 30/30; studio as data 31/31; the replay app 15/15.zig build(43/43),test-integration(33/33 steps, 349 tests),check-web,test-sdk-version.🤖 Generated with Claude Code