Troubleshooting
Diagnose common Lupinum release, deployment, preview, analytics, and authentication failures.
Start from the failing boundary. Preserve the exact run URL, commit SHA, package version, environment, and first relevant error. Do not fix several systems at once.
npm trusted publishing
Fix OIDC permission and trust-record failures.
Dependency quarantine
Understand a blocked fresh package version.
Vercel
Fix Root Directory and cold workspace builds.
Plausible
Fix script detection and feedback events.
Package previews
Fix missing or unsafe pkg.pr.new previews.
GitHub CLI
Separate sandbox restrictions from real login failures.
Diagnose in order
- Confirm the exact commit and workflow file.
- Find the first failing job and step.
- Separate repository configuration from external service configuration.
- Reproduce only the affected boundary.
- Make one focused correction.
- Rerun the failed path and then the complete gate.
Do not disable a required check to make a release green.