Skip to content

ci: fail when committed dist is stale #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.

Sign up for GitHub

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

Merged
VickyXAI merged 1 commit into from
Aug 7, 2026
Merged

ci: fail when committed dist is stale #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,3 +22,12 @@ jobs:
cache: npm
- run: npm ci
- run: npm run check
# Consumers install this package straight from a commit tarball, which
# runs no build step — they execute the dist/ committed here. `npm run
# check` rebuilds it but never asserts the result matches what is
# checked in, so a change that edits source without rebuilding stays
# green and silently ships a stale artifact to every pinned consumer.
# One matrix leg is enough: the build output does not vary by Node major.
- name: Verify committed dist matches source
if: matrix.node == 20
run: git diff --exit-code -- dist
Loading