changelogs for 1.6.0 - #4692
Conversation
|
|
|
Warning Review limit reached
More reviews will be available in 23 minutes and 42 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (30)
📝 WalkthroughWalkthroughChangelog entries and version files were updated across core, framework, transports, and several plugins. The Makefile gained a JUnit report summary target, and migration tests were adjusted for formatting and decrypted secret assertions. ChangesRelease metadata propagation and test summaries
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 3❌ Failed checks (3 warnings)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
89b5c26 to
0c57f92
Compare

Summary
This PR bumps core to v1.6.0, framework to v1.4.0, and transports to v1.6.0, shipping a batch of new provider integrations, a typed secret-reference system, streaming reliability improvements, and a broad set of bug fixes across Bedrock, Gemini, Anthropic, and the Responses API.
Changes
x-bf-customer-idandx-bf-customer-nameheader support for per-customer attribution (governance plugin)list modelsnow returnsContextLength,MaxInputTokens,MaxOutputTokens,Architecture, andWebSearchpricing from pricing entries; Fireworks models enriched from configSecretVarenv/vault reference support (env.*,vault.*) with store/resolve/remove hooks, replacingEnvVaracross core, framework, and plugins. Note:TableVirtualKey.Valuewas rolled back to a plain string; virtual key values do not support env/vault references in this releaseVaultPathKeyerinterface andmap[string]EnvVarsupport, replacing per-modelBeforeSave/AfterDeletehooks$defsgroup_traces_by_sessionsupport, root-span content logging disable toggle, and typedSecretVarsupporttool_resultorder to match paralleltool_useblocks, and set TTL in cache pointsauthor,recipient, andencrypted_contentin multi-agent items and message copies; accepted object-valued tool-call arguments (e.g.tool_search_call) on the streaming path; populated error message in streaming error eventsCacheDiagnostics/CacheMissReasonschemacloseBodyStreampanic in idle-timeout timer goroutine; dropped assistant reasoning for Cerebrasallow_all_keysandblacklisted_modelsnow sync fromconfig.jsonsource of truth;PUT /api/providers/{provider}no longer silently discardskeys/blocked-model editsBifrostContextKeyAPIKeyIDafterPreRequestHookunblockextra_contentonChatAssistantMessageToolCallfor lossless round-tripping; preserved structured errors for streaming plugin blocks; configurable server logs; raw SQL column-add migrations;responses_input_historyfallback for hybrid logstore logs UIType of change
Affected areas
How to test
x-bf-customer-id/x-bf-customer-nameheaders are forwarded and attributed in logslist modelsreturns enriched fields (ContextLength,MaxInputTokens, etc.)env.*andvault.*references in provider config fields resolve correctly; confirm virtual key values remain plain stringsBreaking changes
EnvVarhas been renamed toSecretVaracross core, framework, and several plugins (jsonparser, maxim, mocker, semanticcache, telemetry). Any code or config referencingEnvVardirectly will need to be updated toSecretVar. Virtual key values (TableVirtualKey.Value) do not support env/vault references in this release; that capability was reverted.Related issues
error.messageon context_length_exceededreasoning_effort"max" silently downgraded to "high"/anthropicendpoint fails after first turn with 400 errorcloseBodyStreamand crash the processparameterskey_ids:["*"]not synced toallow_all_keysfor existing virtual keysPUT /api/providers/{provider}silently discardspayload.KeysSecurity considerations
SecretVarintroduces typed env/vault references for secret fields; ensure vault paths and env variable names do not leak sensitive identifiers in logs or error responsesChecklist
docs/contributing/README.mdand followed the guidelines