-
Notifications
You must be signed in to change notification settings - Fork 298
fix: use minProtocol: 3 instead of args.protocol in connect params #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -76,7 +76,7 @@ export function buildGatewayConnectProfile(args: { | |
| capabilities: string[]; | ||
| }): GatewayConnectProfile { | ||
| const baseParams = { | ||
| minProtocol: args.protocol, | ||
| minProtocol: 3, | ||
| maxProtocol: args.protocol, | ||
|
Comment on lines
+79
to
80
|
||
| role: "operator" as const, | ||
| scopes: [...OPERATOR_SCOPES], | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There doesn't appear to be a unit test asserting the
connectrequest includesminProtocol/maxProtocolwith the expected values (the existingtests/unit/openclawAdapter.test.tsinspectsclientandcapsbut not protocol params). Adding an assertion would prevent regressions like this from reappearing and matches the test plan described in the PR.