Repository navigation
sdk: release 0.2.31 - #611
Merged
Merged
Conversation
`sdk_version` goes from 0.2.30 to 0.2.31. Merging tags `sdk-v0.2.31` and publishes its tarball. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
foxnne
enabled auto-merge (squash)
October 19, 2026 03:22
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
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.
What changes
sdk_versiongoes from 0.2.30 to 0.2.31. Merging this tagssdk-v0.2.31and publishes its tarball.sdk-repinthen asks each store plugin to repin.Why now: the SDK's shape has moved several times since 0.2.30. Store plugins and apps built on fizzy, Graphl among them, only get the new calls once they're released. Most of them come from Graphl's report.
SDK impact
sdk/src/version.zig,sdk_versionuntouched, PR labelledsdksdk_version, lists thesdkPRs since the lastsdk-v*tagsdkPRs sincesdk-v0.2.30:host.pluginDataFolder(plugin)gives<config>/plugin-data/<id>, made on first ask. It's the plugin's own fromregisterthroughdeinit, and stays on disk after uninstall.Host.retirePluginunregisters a plugin, runs itsdeinit, then tells the app, so a plugin can still write out state indeinit. OnEditorAPI,pluginUnregisteredbecamepluginRetired; that vtable is implemented by the app, not by plugins.host.hideSurface(id)shuts the tray whose shown view isid, or closes a float that holds onlyid. Anything else returns false. Mid-frame it acts after the frame has drawn. A toggle isif (!host.hideSurface(id)) _ = host.revealSurface(id);.host.recentFolderOpened(i)returns when recent folderiwas opened, in Unix seconds, or null if unknown.recentFolderAtis unchanged.sdk.keywords.ide.homeis new. While the workbench's pane is empty, it shows a surface keywordedhomein place of its own page. The fingerprint didn't move; a plugin on an older SDK can write&.{"home"}.fizzy.history.undone, with a payload typeevents.StepTaken. Additive; the fingerprint didn't move.restoreHistoryhook andsdk.Plugin.RestoredHistory. Plugins without the hook are unaffected.Core change plugins pick up at this release (no boundary change): #550, a replayed backdrop captures inside a front-to-back block. (
app/changes since 0.2.30, such as #570 and #602, are not compiled into plugins.)Verified
scripts/check-fmt.shandzig build test-sdk-versionpass. The fingerprint is main's recorded value; onlysdk_versionchanged.Follow-ups
sdk-repinopens their PRs.gh workflow run web.yml --ref main -f go_live=0.2.31.🤖 Generated with Claude Code