Skip to content

fix(deps): update dependency @kaitranntt/ccs to ^7.13.0 #496

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.

Sign up for GitHub

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

Merged
renovate merged 1 commit into from
Jan 4, 2026
Merged

fix(deps): update dependency @kaitranntt/ccs to ^7.13.0 #496

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion bun.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
"@getgrit/cli": "^0.1.0-alpha.1743007075",
"@github/copilot": "^0.0.374",
"@google/jules": "^0.1.42",
"@kaitranntt/ccs": "^7.12.1",
"@kaitranntt/ccs": "^7.13.0",

@mesa-dot-dev mesa-dot-dev Bot Jan 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Medium

This update includes a critical fix for CLIProxy OAuth account discovery (issue #242 - adding kiro/ghcp provider mappings to discoverExistingAccounts). Since this codebase heavily uses cliproxyapi with OAuth auth sync (see home-manager/services/cliproxyapi/), this fix is particularly relevant.

Consider:

  1. Testing the cliproxyapi service after deployment to verify OAuth account discovery works correctly with the fix
  2. Reviewing config/cliproxyapi/config.yaml to ensure it's compatible with the new version
  3. Checking if the new MiniMax provider support requires any configuration updates

The update also includes race condition fixes and improved validation logic that should improve overall stability of the ccs/cliproxyapi integration.

Agent: 🏛 Architecture • Fix in Cursor • Fix in Claude

Prompt for Agent 
Task: Address review feedback left on GitHub.
Repository: shunkakinoki/dotfiles#496
File: package.json#L20
Action: Open this file location in your editor, inspect the highlighted code, and resolve the issue described below.

Feedback:
This update includes a critical fix for CLIProxy OAuth account discovery (issue #242 - adding kiro/ghcp provider mappings to discoverExistingAccounts). Since this codebase heavily uses cliproxyapi with OAuth auth sync (see home-manager/services/cliproxyapi/), this fix is particularly relevant.

Consider:
1. Testing the cliproxyapi service after deployment to verify OAuth account discovery works correctly with the fix
2. Reviewing config/cliproxyapi/config.yaml to ensure it's compatible with the new version
3. Checking if the new MiniMax provider support requires any configuration updates

The update also includes race condition fixes and improved validation logic that should improve overall stability of the ccs/cliproxyapi integration.

"@nanocollective/nanocoder": "^1.19.2",
"@pulumi/pulumi": "^3.214.0",
"@sourcegraph/amp": "^0.0.1767254483-g812f6b",
Expand Down
Loading