Repository navigation
Conversation
CI installs frozen, so an out-of-sync lockfile fails every job in its setup step rather than in a step that names the cause - every open PR was red on Secrets and Check Lint Run with runner noise in the log and no error. A chore(release) bumped @lunora/observability to alpha.20 and @lunora/platform-cloudflare to alpha.12 in packages/do/package.json; the follow-up lockfile sync did not cover it. Regenerated with pnpm install --lockfile-only, never hand-edited. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011sk9BLaUZDkPVAZ1sKhuDP
✅ Deploy Preview for lunorash ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
CI is red on every open PR, and this is why
A
chore(release)bumped both inpackages/do/package.json; the follow-up "sync pnpm-lock.yaml with released manifests" commit did not cover that manifest.Why it was hard to see
CI installs frozen, so this fails inside the shared "Setup resources and environment" step — before any job reaches the thing it is named after. Every open PR shows
SecretsandCheck Lint Runfailing, and the job log is entirely runner-infrastructure noise with no error in it. The dependency PRs (#380–#383) show twenty-plus failures for the same single reason.It reproduces locally in one command:
pnpm install --frozen-lockfileonalphaexits 1 with the message above.The tell was ambient rather than in the logs — a
pnpm-lock.yamldiff kept appearing in my worktree after unrelated commands. That was pnpm repairing the lockfile each time, and I kept reverting it as stray drift.The fix
Regenerated with
pnpm install --lockfile-only— never hand-edited, per the repo rule that a hand-resolved lockfile installs a tree nobody has.The diff is the two specifier bumps plus pnpm reshuffling which consumers link to the workspace and which resolve from the registry, which is ordinary behaviour with exact sibling pins (the lockfile already carried registry-resolved
@lunora/*entries before this change). No dependency tree change.Verification
pnpm install --frozen-lockfileexits 0 after the change, having exited 1 before it. All seven rootpostinstallgates pass onalphaindependently, so this is the only thing wrong.Merge this first — every other open PR is blocked behind it, including #390.
🤖 Generated with Claude Code
https://claude.ai/code/session_011sk9BLaUZDkPVAZ1sKhuDP