fix(release): make gitHead verification optional for tarball-published artifacts - #24
Merged
Merged
Conversation
GhostAPI PR safetyResult: success The status check and sanitized evidence artifact are the source of truth. This comment is updated in place and contains no request traffic or secrets. |
yiaany
force-pushed
the
fix/registry-githead-optional
branch
from
September 1, 2026 13:26
3998ac1 to
f7fad56
Compare
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.
Publishing an explicit tarball does not automatically populate the npm registry gitHead metadata field. This PR relaxes the script to verify gitHead only if the registry populated it, so GitHub Release creation is not blocked.