chore: commit package-lock.json to unblock npm publish workflow#3
Merged
chore: commit package-lock.json to unblock npm publish workflow#3
Conversation
Agent-Logs-Url: https://github.com/Foscat/Interactive-Surface-CSS/sessions/bb1431ce-61b3-4671-902b-f353e46cfd7b Co-authored-by: Foscat <40616718+Foscat@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
Foscat
April 4, 2026 21:49
View session
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.
Summary
package-lock.jsonwas listed in.gitignore, causingactions/setup-node@v4(withcache: npm) to fail beforenpm cicould run — blocking every publish attempt.Removes
package-lock.jsonfrom.gitignoreand commits the generated lock file.Scope
Validation
npm install # generated package-lock.json, 0 vulnerabilitiesAPI and Behavior Impact
Documentation
Notes
After merging to
main, re-run the "Publish to npm" workflow (or push a new tag). Thenpm cistep will now resolve correctly.