Skip to content

fix: sync pnpm-lock.yaml with SDK bump to 8f3a123#159

Open
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:fix/sync-sdk-lockfile
Open

fix: sync pnpm-lock.yaml with SDK bump to 8f3a123#159
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:fix/sync-sdk-lockfile

Conversation

@0x-SquidSol
Copy link
Copy Markdown
Contributor

Summary

  • Issue: package.json pins @percolator/sdk to commit 8f3a123 (latest main), but pnpm-lock.yaml still resolved to the old commit 9d965f4. The Dockerfile uses pnpm install --frozen-lockfile, which would fail the build due to this mismatch — blocking new deployments.
  • Fix: Regenerated pnpm-lock.yaml via pnpm install so both files agree on SDK commit 8f3a123.

Verification

  • pnpm install --frozen-lockfile passes (simulates Docker build)
  • tsc --noEmit passes (zero type errors)
  • vitest run passes (186/186 tests)
  • SDK specifier in lockfile confirmed as 8f3a123

🤖 Generated with Claude Code

package.json was updated to pin @percolator/sdk at commit 8f3a123
(latest main) but pnpm-lock.yaml still resolved to the old commit
9d965f4. Since the Dockerfile uses `pnpm install --frozen-lockfile`,
this mismatch would cause Docker builds to fail.

Regenerates pnpm-lock.yaml so both files agree on SDK 8f3a123.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 9, 2026

Warning

Rate limit exceeded

@0x-SquidSol has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 55 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 55 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 19db86eb-36b8-455d-b9e6-f53abb1e4cea

📥 Commits

Reviewing files that changed from the base of the PR and between fb94c29 and c9caf3e.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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 and usage tips.

@0x-SquidSol
Copy link
Copy Markdown
Contributor Author

⚠️ This PR is now redundant — please close

The SDK has since been migrated from the GitHub commit-pinned @percolator/sdk to the npm-published @percolatorct/sdk@1.0.0-beta.13 (merged via direct commits to main including b23abae, e9c72c9, and subsequent beta bumps up to ed06944).

This PR was syncing pnpm-lock.yaml for the old @percolator/sdk#8f3a123 commit, which no longer exists in package.json. The lockfile mismatch it fixed has been superseded by the full SDK migration.

Action: Safe to close without merging.

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