Repository navigation
Fix #1: bootstrap/scaffolding CI stability - #7
Merged
Merged
Conversation
Recreate the npm lockfile to avoid the invalid version metadata issue that caused bootstrap CI to fail, so the scaffolding branch can be reviewed and merged through the PR gate.
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.
Issues
Summary
package-lock.jsonto remove invalid optional dependency metadata that brokenpm ciin GitHub Actions.npm ci,npm run check,npm run build) pass locally on the scaffolding branch.How to test
npm cinpm run checknpm run buildNotes
maincame from the initial bootstrap commit; this PR is the corrective bootstrap/scaffolding PR for review.