fix: harden the release verify job - #52
Merged
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
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.
The first release published all 8 packages with provenance, but the
verifyjob failed. Two independent defects, both fixed.openclawin as an auto-installed peer dependency, putting 325 unrelated packages in the audit scope and failing on an aliased dependency inside that tree. It now installs with--omit=peer.docs/releasing.mddocuments both commands and the conditions under which npm skips provenance without failing.Includes a patch changeset on
@paleo/openclaw-test, with no functional change, so that merging this exercises the corrected job on a real release. That package is a leaf, so the release covers it alone, and itsopenclawpeer dependency is what triggered the failure.