Skip to content

fix(providers): remove invalid CodeBuddy CN glm-4.7 and add hy3 (0.0x… - #10356

Open
rizxfrog wants to merge 7 commits into
diegosouzapw:release/v3.8.50from
rizxfrog:chore/correct_model_id
Open

fix(providers): remove invalid CodeBuddy CN glm-4.7 and add hy3 (0.0x…#10356
rizxfrog wants to merge 7 commits into
diegosouzapw:release/v3.8.50from
rizxfrog:chore/correct_model_id

Conversation

@rizxfrog

Copy link
Copy Markdown
image image Codebuddy has removed the glm-4.7 model and added the hy3 free model

diegosouzapw and others added 6 commits August 8, 2026 00:08
…ouzapw#189, diegosouzapw#190)

Bumps: nanoid ^3.3.17 (was transitive, now overridden), dompurify ^3.4.13
(with monaco-editor scoped override). Closes Dependabot diegosouzapw#189, diegosouzapw#190.

Remaining diegosouzapw#182-diegosouzapw#188 (js-yaml + mermaid) already closed by diegosouzapw#9651 merge —
awaiting Dependabot re-scan.

npm audit → 0 vulnerabilities.
…egosouzapw#190

Closes Dependabot diegosouzapw#189 (dompurify 3.4.13) and diegosouzapw#190 (nanoid 3.3.17). npm audit → 0.
_tasks is a SEPARATE nested git repo (gitignored). The pattern _tasks/ (trailing
slash) ignores only a directory, not a SYMLINK named _tasks. A self-referential
_tasks symlink can slip in via git add -A and, once pulled, checkout materializes
it over the real _tasks repo (destroying plans/specs/hands-off). Anchored /_tasks
ignores the symlink too, preventing re-capture.
…pw#10026)

Mirror the request-time exclusion rule (provider_specific_data.excludedModels)
in the unified catalog builder: a model is hidden when its provider has
connections but none of them is eligible for it. Applied across the
PROVIDER_MODELS, synced, custom, alias-backed, and managed-fallback loops
so ghost models no longer appear as available.

Co-authored-by: ritheshcn25 <ritheshcn25@users.noreply.github.com>
…osouzapw#10055)

* fix(models): memoize getModelsDevPricing for /v1/models catalog

resolveCatalogPricing called getModelsDevPricing once per model while
building GET /v1/models. Each call re-scanned models_dev_pricing and
JSON.parsed every row (~10k SQL scans + multi-GB parse work), pegging
the event loop so even /healthz timed out (diegosouzapw#9685, diegosouzapw#10052).

Memoize the parsed map until saveModelsDevPricing / clearModelsDevPricing
and add a unit test for invalidation.

Signed-off-by: Ravi Tharuma <RaviTharuma@users.noreply.github.com>

* fix(db): invalidate modelsDevPricing cache on DB reset (diegosouzapw#10055)

Copilot review fixes:
1. Register invalidateModelsDevPricingCache() with DB state reset system
   so resetDbInstance() clears the process-local memo, preventing stale
   pricing data from surviving across DB reset/restore operations.
2. Add test assertion verifying DB reset bypasses the memo (Copilot diegosouzapw#10055).

The process-local memo at modelsDevSync.ts:204 caches getModelsDevPricing()
results until saveModelsDevPricing()/clearModelsDevPricing() to avoid
re-scanning all pricing rows on every /v1/models request. Without this hook,
backup restore and test DB resets would serve stale cached data from the
previous connection.

Tests: npm run test:unit:serial -- tests/unit/modelsDevSync-extended.test.ts

---------

Signed-off-by: Ravi Tharuma <RaviTharuma@users.noreply.github.com>
Co-authored-by: Ravi Tharuma <RaviTharuma@users.noreply.github.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
… credit)

Swap the GLM-4.7 model for the Hunyuan hy3 model in the codebuddy-cn
registry, keep the catalog at 15 models, and update the matching provider
test expectations. Regenerated the auto-generated provider reference doc.
@rizxfrog
rizxfrog requested a review from diegosouzapw as a code owner August 14, 2026 06:22
@diegosouzapw

Copy link
Copy Markdown
Owner

Thanks for this — verified against a live test run and it's a solid, well-scoped fix: removing the deprecated glm-4.7 id and adding hy3 (alongside the existing hy3-preview) for CodeBuddy CN, with the model-id test list updated to match. All 12 tests in tests/unit/codebuddy-cn-provider.test.ts pass on this branch.

One thing I'll need to handle on the maintainer side before merging: this PR is targeting main, but our active development branch is release/v3.8.50 (the repo default). I'll retarget the base — the same two edit sites (glm-4.7 / hy3-preview) are unchanged there, so it should apply cleanly without any extra work from you.

No other changes requested. The PROVIDER_REFERENCE.md diff is just the auto-regen doing its usual full-table realignment — nothing to worry about there.

… credit)

Merge release/v3.8.50 into the contributor branch: resolve stale
base-evolution conflicts to the release tip, keeping only the CodeBuddy CN
registry swap of glm-4.7 for hy3 and the matching provider test expectation.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
@diegosouzapw
diegosouzapw changed the base branch from main to release/v3.8.50 August 15, 2026 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants