ci: publish WASM command packages manually, not in CI#107
Merged
Conversation
Removes the build-commands job from publish.yaml and stops CI from publishing the WASM-bearing @secure-exec/core (excluded in scripts/publish/src/lib/packages.ts). WASM-bearing packages (@secure-exec/core + the @agent-os-pkgs/* registry software) are now always published manually; documented in CLAUDE.md -> Publishing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
railway-app
Bot
temporarily deployed
to
secure-exec / secure-exec-pr-107
railway-app
Bot
temporarily deployed
to
rivet-frontend / secure-exec-pr-107
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
CI no longer builds or publishes WASM command binaries.
build-commandsjob from.github/workflows/publish.yaml(and the artifact restore steps inpublish-npm).@secure-exec/corefrom the CI publish set (scripts/publish/src/lib/packages.ts), since it vendors the WASM commands and itsprepack --requirerefuses to ship without them.CLAUDE.md → Publishing.Why
Building WASM in CI was slow/flaky and repeatedly shipped tarballs missing the command set (the
wasm/output is a gitignored build artifact). WASM-bearing packages (@secure-exec/core+ the@agent-os-pkgs/*registry software) are now always published manually.Note / follow-up
With
@secure-exec/coreexcluded from CI publish, after a CI release you must manually publish@secure-exec/coreat the matching version or dependents resolving@secure-exec/core@<version>will fail.