This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
ReleasePort's take
Light signalThe Z.AI API's default model has been updated from `glm-5.2[1m]` to `glm-5.2` due to rejection by the API.
Why it matters: If your application relies on the previous default, explicit selection is now required; no version threshold or deadline applies.
Summary
AI summaryDefault Z.AI model changed from glm-5.2[1m] to glm-5.2 because the former is rejected by the API.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Z.AI default model changed from `glm-5.2[1m]` to `glm-5.2`. Z.AI default model changed from `glm-5.2[1m]` to `glm-5.2`. Source: llm_adapter@2026-06-13 Confidence: high |
— |
| Bugfix | Low |
Removed unsupported `[1m]` suffix variant `glm-5.2[1m]` from Z.AI provider model lists. Removed unsupported `[1m]` suffix variant `glm-5.2[1m]` from Z.AI provider model lists. Source: granite4.1:30b@2026-06-13-audit Confidence: low |
— |
Full changelog
Hotfix: the Z.AI default was
glm-5.2[1m], but the API rejects that id ("Unknown Model", code 1211) — so a fresh Z.AI session failed on its first request. The default is now plainglm-5.2(which works), and the non-working[1m]variant is removed from the picker.
Fixed
- Z.AI default model
glm-5.2[1m]returned "Unknown Model". The 1M-context
[1m]suffix from the devpack docs isn't accepted by the Z.AI chat API
endpoints Codeep uses, so it 400'd on every request. The default (and
cold-start default) is nowglm-5.2, andglm-5.2[1m]is dropped from all
four Z.AI providers' model lists. If your config still points at
glm-5.2[1m], switch with/model glm-5.2.
Breaking Changes
- Removed default and picker entry for Z.AI model `glm-5.2[1m]`; new default is plain `glm-5.2`.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Codeep
All releases →Related context
Related tools
Earlier breaking changes
- v2.8.0 `codeep account push` and `account sync` no longer transfer API keys unless `/keysync on` is enabled
- v2.4.1 MiniMax M3 replaces MiniMax-M2.7 as default model across all providers.
- v2.0.0 McpServer protocol now optional fields `command`, `args`, plus new `url` and `headers`; version bumped to 2.0.0.
Beta — feedback welcome: [email protected]