This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+1 more
Affected surfaces
ReleasePort's take
Light signalConcord v2.2.0 now stores authentication tokens in the system keychain, which triggers a required re‑login after upgrading.
Why it matters: Post‑upgrade users must re‑authenticate; plan for login prompts and user communication when deploying v2.2.0.
Summary
AI summaryConcord now saves tokens in the system keychain, requiring re‑login after upgrade.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Save token in system keychain for authentication. Save token in system keychain for authentication. Source: llm_adapter@2026-06-10 Confidence: high |
— |
| Feature | Medium |
Move UI state to XDG_STATE_HOME directory. Move UI state to XDG_STATE_HOME directory. Source: llm_adapter@2026-06-10 Confidence: high |
— |
| Feature | Low |
Wrap message text at word boundaries in UI. Wrap message text at word boundaries in UI. Source: llm_adapter@2026-06-10 Confidence: high |
— |
Full changelog
Release Notes
Concord save token in system keychain and use it for authentication, so you may need to re-login after this update.
Documentation
- Update homebrew installation by @chojs23
- Update image by @chojs23
Features
Breaking Changes
- Token authentication now uses the system keychain; existing stored tokens are invalid, requiring re‑login.
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 Concord
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]