fix: make release tarball install wp-codebox binary#618
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.
Summary
wp-codeboxbin mapping so the GitHub Release workspace tarball can be installed as a stable binary path instead of requiring a local feature worktree.npm run package-installed-binary-smoke, which packs the root release tarball, installs it into a temporary global prefix, and verifies the installedwp-codeboxbinary can emit the command catalog.v0.4.0includes the fresh sandbox session fix and Codex recipe, but its release asset predates this bin mapping and needs a new approved release tarball.Closes #506.
Verification
npm run package-distribution-smokenpm run package-installed-binary-smokenode -e 'JSON.parse(require("fs").readFileSync("examples/recipes/cookbook/codex-agent-smoke.json", "utf8")); console.log("codex-agent-smoke.json valid")'Release note
No npm publish, tag, GitHub Release, or registry mutation was performed. After merge, the release-manager path is:
If npm publishing is approved, publish all scoped packages from the same clean release commit:
The expected GitHub Release tarball asset from the current package version is
wp-codebox-workspace-0.5.0.tgz.AI assistance