Skip to content

chore(submodules): bump Pmoves-cipher to main 1c9b285 (build fixes #6) - #2062

Merged
POWERFULMOVES merged 1 commit into
mainfrom
chore/cipher-gitlink-build-fixes
Jul 11, 2026
Merged

chore(submodules): bump Pmoves-cipher to main 1c9b285 (build fixes #6)#2062
POWERFULMOVES merged 1 commit into
mainfrom
chore/cipher-gitlink-build-fixes

Conversation

@POWERFULMOVES

Copy link
Copy Markdown
Owner

Promotes the Pmoves-cipher gitlink to the post-squash main tip carrying Pmoves-cipher #6:

  • node-gyp header fetches pinned to the official nodejs.org/dist mirror — unofficial-builds.nodejs.org (alpine/musl node's default) reproducibly ECONNRESET, killing better-sqlite3's compile and aborting overlay-up-agents.
  • pnpm-workspace.yaml gains the packages field pnpm 9 requires (packages field missing or empty on any pnpm run otherwise).

Gitlink targets the squash-merge commit on cipher main (not the branch tip), per the submodule-gitlink-gate fast-forward requirement.

Verified on b850: docker compose build cipher-api from the overlay stack completes end-to-end with this tree.

🤖 Generated with Claude Code

GRAPHITI_MARK: B850-CLAUDE::CIPHER-GITLINK-BUILD-FIXES::2026-07-11

Pmoves-cipher #6 (squash-merged): node-gyp pinned to the official
nodejs.org/dist headers mirror (unofficial-builds.nodejs.org ECONNRESET
killed better-sqlite3's musl compile) + pnpm-workspace.yaml packages field
(pnpm 9 in the Dockerfile errors 'packages field missing or empty' without
it). Gitlink points at the post-squash main tip so the submodule-gitlink
gate sees fast-forward, not a sibling branch commit.

Verified on b850: full cipher-api overlay build completes with this tree
(Image pmoves-cipher-api Built).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@POWERFULMOVES, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 924b58f2-616b-4edc-b310-74e007ecab82

📥 Commits

Reviewing files that changed from the base of the PR and between 49a054a and 6111f11.

📒 Files selected for processing (1)
  • Pmoves-cipher
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/cipher-gitlink-build-fixes

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@POWERFULMOVES
POWERFULMOVES merged commit c117eb5 into main Jul 11, 2026
33 checks passed
@POWERFULMOVES
POWERFULMOVES deleted the chore/cipher-gitlink-build-fixes branch July 11, 2026 14:13
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