-
Notifications
You must be signed in to change notification settings - Fork 1
chore: validate package-lock.json sync in release workflow #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -15,6 +15,10 @@ jobs: | |||||
| - uses: actions/setup-node@v4 | ||||||
| with: | ||||||
| node-version: 20 | ||||||
| - name: Validate lockfile | ||||||
| run: | | ||||||
| npm install --package-lock-only | ||||||
| git diff --exit-code package-lock.json || (echo "package-lock.json is out of sync. Run 'npm install' and commit the changes." && exit 1) | ||||||
|
||||||
| git diff --exit-code package-lock.json || (echo "package-lock.json is out of sync. Run 'npm install' and commit the changes." && exit 1) | |
| git diff --exit-code package-lock.json || (echo "package-lock.json is out of sync. Run 'npm install --package-lock-only' and commit the changes." && exit 1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The lockfile validation step is placed only in the
buildjob but not in thepublish-npmjob. Sincepublish-npmruns independently (after checkout), it should also validate the lockfile before runningnpm cito ensure consistency at the point of actual publishing.Consider either:
publish-npmjob before line 43, or