feat(build): ship step-skill variants as one bundle per group#243
Merged
Conversation
The four integration-v2 step groups expanded to 148 near-identical zips in the release. `packaging: bundle` ships each group as a single JSON holding every variant, so the release carries 144 artifacts instead of 288. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
The menu entry lists each variant's id/framework/default, so a consumer resolves a bundled variant exactly as it does a per-skill zip and the bundle itself stays a plain map of files. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The emitter lived in the full builder alone, so a partial rebuild rewrote a zip nobody serves and left the bundle stale, and the dev server had no route for it. Both callers now share writeBundles, which merges a rebuilt variant into its group so the rest survive. The release uploads the bundle JSONs — without this every bundle download 404s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sarahxsanders
approved these changes
Jul 16, 2026
sarahxsanders
left a comment
sarahxsanders
left a comment
Collaborator
There was a problem hiding this comment.
are there any noticeable performance differences with JSON vs. zip with file sizes being larger? more-so curious
| : {}; | ||
| const bundle = { id: group, variants: { ...existing } }; | ||
| for (const skill of variants) { | ||
| bundle.variants[skill.shortId] = readSkillFiles(path.join(sourceDir, skill.id)); |
Collaborator
There was a problem hiding this comment.
should we validate IDs per bundle? I think if any duplicates slip through they could overwrite
Collaborator
Author
There was a problem hiding this comment.
Oh good call, there should be
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
The four integration-v2 step groups expanded to 148 near-identical zips, so
packaging: bundlenow ships each group as one JSON holding every variant and the release carries 144 artifacts instead of 288.