fix(cli): pin relayflows dependency exactly - #1417
Draft
willwashburn wants to merge 1 commit into
Draft
Conversation
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.