Check staged moshcode upgrades before replacing the working package - #117
Merged
Merged
Conversation
ThreatCrush Security Scan20 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 13 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
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 public installer currently replaces the working CLI before npm installs its runtime dependencies. Install dependencies and check CLI startup in staging so a failed update leaves the existing package runnable. Dependency-free releases continue to skip npm.
Validation: all 250 tests passed, production Next.js build passed, POSIX shell syntax passed. Regression tests exercise fresh installs, successful updates, dependency-install failures, and missing dependencies after npm reports success.