Repository navigation
fix: restart a daemon from an older version and render root instances - #53
Merged
Merged
Conversation
- the daemon reports its version and code path in /health; figma-cli restarts it on a mismatch so render-batch and eval never run stale code after an update - a lone <Instance> is a valid root for render and render-batch - agent rules and the eval output limit mention verify --scale for sharper screenshots - release 2.2.4 Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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.
What changes
Stale daemon after an update
render-batchandevalrun inside the background daemon. Afternpm updatethe old daemon kept serving them with the previous version's code until it idled out (up to 60 minutes), so new features seemed missing. The daemon now reports its version and code path in/health, and figma-cli restarts it when they do not match its own.Instances as the root
render '<Instance component="Card" />'andrender-batchwith a list of instances place them directly on the page. Before this they failed with "must start with ".Sharper screenshots
The agent rules and the
evaloutput limit point tofigma-cli verify <id> --scale 2.Release 2.2.4.
🤖 Generated with Claude Code