fix(release): restore pnpm package artifacts#104975
Merged
Merged
Conversation
Contributor
Author
|
Land-ready verification for exact head
Known gap: the immutable |
vincentkoc
pushed a commit
that referenced
this pull request
Jul 12, 2026
(cherry picked from commit 0a2a6a2)
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 Problem This Solves
The July release branch invokes
scripts/package-openclaw-for-docker.mjs --pnpm-packfor Parallels package artifacts, but the helper implementation was omitted from the backport. Beta release checks therefore reject the flag and cannot produce the package artifact.Why This Change Was Made
Restore the already-proven main implementation on
release/2026.7.1, while preserving the July-only unreleased-changelog option. The helper now parses the flag, invokespnpm pack, discovers the tarball only inside the freshly emptied output directory, and rejects incompatible npm metadata output.User Impact
July and subsequent beta candidates can build the self-contained Parallels package artifact again. Existing npm-based package paths are unchanged.
Evidence
tbx_01kxaa8b2439146164hqbychp4): package helper 25/25 passed.git diff --checkpassed.Fixes the deterministic package failures in beta release-check run 29179313396.