Skip to content

ci(prober): npm ci fallback to npm install (robust self-bootstrapping deploy) - #81

Merged
ralyodio merged 1 commit into
masterfrom
harden-prober-provision
Jul 5, 2026
Merged

ralyodio merged 1 commit into
masterfrom
harden-prober-provision

Conversation

@ralyodio

@ralyodio ralyodio commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Why

The deploy-prober run failed at the prober build step:

npm error The `npm ci` command can only install with an existing package-lock.json

At that commit prober/package-lock.json wasn't committed yet. It exists on master now (lockfileVersion 3, bullmq/ioredis in sync), so a re-run would already pass — but a self-bootstrapping deploy shouldn't hard-fail on a missing/stale lock.

Fix

npm ci … || npm install … in provision.sh. Reproducible install when the lock is good; graceful fallback otherwise.

🤖 Generated with Claude Code

…ock)

The deploy-prober run failed at 'npm ci' because prober/package-lock.json was
absent at that commit. Harden provision.sh so a missing or out-of-sync lockfile
falls back to 'npm install' instead of hard-failing the self-bootstrapping
deploy.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 5, 2026

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

@ralyodio
ralyodio merged commit 119a824 into master Jul 5, 2026
8 checks passed
@ralyodio
ralyodio deleted the harden-prober-provision branch July 5, 2026 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant