fix(module): use awsl v7 module path#9
Conversation
|
Important Review skippedToo many files! This PR contains 477 files, which is 327 over the limit of 150. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (477)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
|
Closing this PR because it cannot pass repository policy in its current shape. What was verified: This passed on the branch, and maxx also compiled its CLIProxyAPI adapters with this branch through a temporary local replace: Why this PR is being closed: I tried to create that issue, but Issues are disabled on this repository. Current blocker for maxx remains:
So the fix needs to happen through the repository's allowed maintenance path, not via this blocked PR shape. |
Summary
github.com/awsl-project/CLIProxyAPI/v7sdk/execimports from stale v6 internals to v7 internalsmaininstead of rewriting the stale fix: use awsl module path for v7 sdk #5 branchValidation
go test ./sdk/exec ./sdk/cliproxy/auth ./sdk/cliproxy/executor ./sdk/translatorgo test ./internal/adapter/provider/cliproxyapi_codex ./internal/adapter/provider/cliproxyapi_antigravityNotes
This unblocks maxx from updating its CLIProxyAPI dependency without hitting either module-path mismatch or
internal package not allowederrors.