fix(cli): pin relayflows dependency exactly - #1417
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent 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 (3)
📝 WalkthroughWalkthroughThe CLI package now pins ChangesCLI dependency pinning
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: Poem
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Summary
@relayflows/clicaret range with the exact version already resolved by this repository (1.0.1)Companion to AgentWorkforce/relayflows#25 and AgentWorkforce/relayflows#27.
Security sequencing
This pin is a reproducibility control, not the leak remediation by itself. Every currently published Relayflows version checked, including
1.0.1, contains the first-run observer-key leak. The leak closes only after the Relayflows fix is reviewed and published, followed by an explicit bump of this pin to that safe release. Until then, this PR must not be described as an all-clear.The installed tree on the machine that runs Agent Relay must be checked after that bump, dependencies included. A clean package tarball cannot establish closure because
npm packomitsnode_modules.Verification
npm ciaccepts the exact package/lock declarationnpx vitest run packages/cli/src/cli/entrypoint.test.ts— 5/5 passednpm run build:core && npm run build:cligit diff --checkNo packages were published and no release was created.