chore(persona-kit): bump @relayfile/adapter-core ^0.3.13 → ^0.3.17 (gmail + more in trigger catalog)#144
Conversation
persona-kit imports the trigger catalog from `@relayfile/adapter-core/triggers` at runtime, so its `KNOWN_TRIGGER_CATALOG` is whatever core resolves to. The monorepo lockfile was pinned at 0.3.13 (23 providers, no gmail). 0.3.17 adds gmail (`file.created`/`file.updated`/`file.deleted`, from relayfile-adapters #119) and others — 25 providers total. Bump the declared floor and refresh the lock so the monorepo + the next release resolve 0.3.17, enabling gmail trigger autocomplete + deploy-time lint. (Downstream npm consumers on the `^0.3.13` caret already resolved 0.3.17 on a fresh install; this makes the minimum explicit and updates the in-repo pin.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 36 minutes and 28 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
1 participant
What
Bumps
@agentworkforce/persona-kit's@relayfile/adapter-coredependency^0.3.13→^0.3.17and refreshespnpm-lock.yaml(was pinned at0.3.13).Why
persona-kit consumes the trigger catalog via a runtime import of
@relayfile/adapter-core/triggers, so itsKNOWN_TRIGGER_CATALOGis whatever core resolves to. The lock was stuck at0.3.13(23 providers, no gmail).0.3.17adds gmail (file.created/file.updated/file.deleted, from relayfile-adapters#119) plus others — 25 providers now.Bumping the floor + refreshing the lock makes the monorepo (and the next release) resolve
0.3.17, sodefinePersonagmail trigger autocomplete + deploy-time lint work in-repo and ship in the next persona-kit release.Verification
@relayfile/adapter-core@0.3.17.import('@relayfile/adapter-core/triggers')→KNOWN_TRIGGER_CATALOG.gmail === ["file.created","file.deleted","file.updated"]; 25 providers.pnpm --filter @agentworkforce/persona-kit typecheckclean; 224/224 tests pass.🤖 Generated with Claude Code