Repository navigation
sdk: release 0.2.23 - #367
Merged
Merged
Conversation
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.22 to 0.2.23. Merging tagssdk-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 frommain, and fizzyed.it/app is built frommain. Also, #355 moved thepluginsservice to version 2, and the agent plugin'sfizzy_buildasks for version 1 until it repins.SDK impact
sdk/src/version.zig,sdk_versionuntouched, PR labelledsdksdk_version, lists thesdkPRs since the lastsdk-v*tagThe
sdkPRs sincesdk-v0.2.22:Additive, reaching plugins with this release:
pluginsservice is version 2, withlist(each plugin's identity, link, version, registration counts and status). A caller built for version 1 is refused until it rebuilds, which this release's repin does.sdk/plugin_sdk.zig).Also reaching plugins (
core/):core.viz, graphics for live numbers:line,bar,stat,Table(core: core.viz, graphics for live numbers; the profiler draws with them #345);Pie,keyColor,palette(core: viz.Pie; the profiler shows where a frame went as a pie #347); the table's rounded header and shaded rows (core: viz tables have a rounded header and shaded rows, no border #359).core.profile:lookback(): 30 s of costs and the frames over budget, plusReportOptions.over_ms/.hitchesandselfTimes(core: the profiler keeps 30 s of costs and the frames over budget #353).frameCauses()andReportOptions.causes: why each frame happened (core: the profiler says why each frame happened #364).phase/Phases/ReportOptions.startup: startup timing (app: fizzy times its own startup, and a handover's #365, which landed inside core: the profiler says why each frame happened #364's squash commit).abistays 4.Verified
zig buildandtest-sdk-versionon this head.scripts/pack-sdk.shpacksfizzy-sdk-v0.2.23.tar.gz.main) builds against this tree'ssdk/withzig 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).Follow-ups
fizzyedit/agentandfizzyedit/chatrepin to thesdk-v0.2.23tarball.🤖 Generated with Claude Code