Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions .github/workflows/scripts/run-migration-tests.sh
Original file line number Diff line number Diff line change
Expand Up @@ -453,10 +453,10 @@ VALUES (1, 'migration-test-hash-abc123def456', $now, $now)
ON CONFLICT DO NOTHING;

-- governance_budgets (reset_duration is a string like "1d", "1h", etc.)
INSERT INTO governance_budgets (id, max_limit, current_usage, reset_duration, last_reset, config_hash, created_at, updated_at)
VALUES
('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now),
('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now)
INSERT INTO governance_budgets (id, max_limit, current_usage, reset_duration, last_reset, config_hash, created_at, updated_at, calendar_aligned)
VALUES
('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, 0),
('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, 1)
Comment on lines +458 to +459
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 Integer literals 0/1 incompatible with PostgreSQL BOOLEAN column

The calendar_aligned column is defined in Go as bool with gorm:"default:false", which GORM maps to a native BOOLEAN type in PostgreSQL. PostgreSQL does not accept bare integer literals (0, 1) for BOOLEAN columns and will throw ERROR: column "calendar_aligned" is of type boolean but expression is of type integer, causing the PostgreSQL migration test to fail.

Every other boolean column in this same script uses false/true (e.g. send_back_raw_request/send_back_raw_response in the config_providers insert, and enabled in config_log_store), both of which are valid boolean literals accepted by PostgreSQL and modern SQLite (≥ 3.23.0) alike.

Suggested change
('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, 0),
('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, 1)
('budget-migration-test-1', 1000.00, 100.00, '1d', $now, 'budget-hash-001', $now, $now, false),
('budget-migration-test-2', 5000.00, 250.00, '7d', $now, 'budget-hash-002', $now, $now, true)

ON CONFLICT DO NOTHING;

-- governance_rate_limits (flexible duration format with token_* and request_* columns)
Expand Down
4 changes: 4 additions & 0 deletions core/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
- fix: fixed timeout status code handling across all providers
- fix: preserve cached provider metadata on cross-provider cache hits
- fix: prevent reasoning text from leaking into Gemini response content
- feat: added Anthropic beta headers support
2 changes: 1 addition & 1 deletion core/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.15
1.4.16
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 5 additions & 1 deletion docs/providers/supported-providers/azure.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -39,14 +39,18 @@ Azure is a cloud provider offering access to OpenAI and Anthropic models through

## Beta Headers

For Anthropic models on Azure, Bifrost validates `anthropic-beta` headers. Azure supports most Anthropic beta features.
For Anthropic models on Azure, Bifrost validates `anthropic-beta` headers and drops unsupported headers from the request. Azure supports most Anthropic beta features.

**Supported**: `computer-use-*`, `structured-outputs-*`, `advanced-tool-use-*`, `mcp-client-*`, `prompt-caching-scope-*`, `compact-*`, `context-management-*`, `files-api-*`, `interleaved-thinking-*`, `skills-*`, `context-1m-*`, `redact-thinking-*`

**Not supported**: `fast-mode-*`

You can override these defaults per provider via the **Beta Headers** tab in provider configuration or via [`beta_header_overrides`](/quickstart/gateway/provider-configuration#beta-header-overrides). See the full support matrix in the [Anthropic provider docs](/providers/supported-providers/anthropic#beta-headers).

<Frame>
<img src="/media/azure-setting-anthropic-beta-headers.png" alt="Azure Beta Headers configuration tab showing supported and unsupported Anthropic beta features with override options" />
</Frame>

---

# 1. Chat Completions
Expand Down
7 changes: 6 additions & 1 deletion docs/providers/supported-providers/bedrock.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -53,14 +53,19 @@ AWS Bedrock supports multiple model families (Claude, Nova, Mistral, Llama, Cohe

## Beta Headers

For Claude models on Bedrock, Bifrost validates `anthropic-beta` headers to ensure only supported features are forwarded.
For Claude models on Bedrock, Bifrost validates `anthropic-beta` headers and drops unsupported headers from the request.

**Supported**: `computer-use-*`, `structured-outputs-*`, `compact-*`, `context-management-*`, `interleaved-thinking-*`, `context-1m-*`

**Not supported**: `advanced-tool-use-*`, `mcp-client-*`, `prompt-caching-scope-*`, `files-api-*`, `skills-*`, `fast-mode-*`, `redact-thinking-*`

You can override these defaults per provider via the **Beta Headers** tab in provider configuration or via [`beta_header_overrides`](/quickstart/gateway/provider-configuration#beta-header-overrides). See the full support matrix in the [Anthropic provider docs](/providers/supported-providers/anthropic#beta-headers).


<Frame>
<img src="/media/aws-bedrock-anthropic-beta-headers.png" alt="AWS bedrock Beta Headers configuration tab showing supported and unsupported Anthropic beta features with override options" />
</Frame>

---

# 1. Chat Completions
Expand Down
6 changes: 5 additions & 1 deletion docs/providers/supported-providers/vertex.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -41,14 +41,18 @@ Vertex AI is Google's unified ML platform providing access to Google's Gemini mo

## Beta Headers

For Anthropic models on Vertex AI, Bifrost validates `anthropic-beta` headers to ensure only supported features are forwarded. Unsupported headers are rejected with a clear error.
For Anthropic models on Vertex AI, Bifrost validates `anthropic-beta` headers and drops unsupported headers from the request.

**Supported**: `computer-use-*`, `compact-*`, `context-management-*`, `interleaved-thinking-*`, `context-1m-*`

**Not supported**: `structured-outputs-*`, `advanced-tool-use-*`, `mcp-client-*`, `prompt-caching-scope-*`, `files-api-*`, `skills-*`, `fast-mode-*`, `redact-thinking-*`

You can override these defaults per provider via the **Beta Headers** tab in provider configuration or via [`beta_header_overrides`](/quickstart/gateway/provider-configuration#beta-header-overrides). See the full support matrix in the [Anthropic provider docs](/providers/supported-providers/anthropic#beta-headers).

<Frame>
<img src="/media/vertex-ai-setting-anthropic-beta-headers.png" alt="Vertex AI Beta Headers configuration tab showing supported and unsupported Anthropic beta features with override options" />
</Frame>

---

# 1. Chat Completions
Expand Down
3 changes: 3 additions & 0 deletions framework/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
- feat: added /api/models/details endpoint with model capability metadata
- fix: populate customer virtual_keys in governance APIs
- fix: enterprise model catalog sync improvements
2 changes: 1 addition & 1 deletion framework/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.2.34
1.2.35
1 change: 1 addition & 0 deletions plugins/governance/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- fix: populate customer virtual_keys in governance APIs
2 changes: 1 addition & 1 deletion plugins/governance/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.34
1.4.35
1 change: 1 addition & 0 deletions plugins/jsonparser/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/jsonparser/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.33
1.4.34
1 change: 1 addition & 0 deletions plugins/litellmcompat/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/litellmcompat/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.0.23
0.0.24
1 change: 1 addition & 0 deletions plugins/logging/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/logging/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.34
1.4.35
1 change: 1 addition & 0 deletions plugins/maxim/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/maxim/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.5.33
1.5.34
1 change: 1 addition & 0 deletions plugins/mocker/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/mocker/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.33
1.4.34
1 change: 1 addition & 0 deletions plugins/otel/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/otel/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.1.33
1.1.34
1 change: 1 addition & 0 deletions plugins/semanticcache/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- fix: preserve cached provider metadata on cross-provider cache hits
2 changes: 1 addition & 1 deletion plugins/semanticcache/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.32
1.4.33
1 change: 1 addition & 0 deletions plugins/telemetry/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- chore: upgraded core to v1.4.16 and framework to v1.2.35
2 changes: 1 addition & 1 deletion plugins/telemetry/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.34
1.4.35
19 changes: 19 additions & 0 deletions transports/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
## ✨ Features

- **Model Details API** — Added /api/models/details endpoint for model capability metadata
- **Anthropic Beta Headers** — Support for Anthropic beta feature headers in requests

## 🐞 Fixed

- **Reasoning Content Leak** — Prevented reasoning text from leaking into Gemini response content
- **Timeout Status Code** — Fixed timeout status code handling across all providers
- **Cross-Provider Cache** — Preserved cached provider metadata on cross-provider cache hits
- **Governance Virtual Keys** — Populated customer virtual_keys in governance APIs
- **List Models Integration** — Removed default provider override on list models request in integrations
- **Client Settings Headers** — Fixed Client settings UI to accept * as allowed headers

## 🔧 Maintenance

- **FIPS Docker Image** — Switched to FIPS-compliant base image for Docker builds
- **Security Hardening** — Applied StepSecurity best practices to CI/CD pipeline (thanks [@step-security-bot](https://github.com/step-security-bot)!)
- **Snyk Fixes** — Addressed Snyk vulnerability findings in Docker configuration
2 changes: 1 addition & 1 deletion transports/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.4.18
1.4.19
Loading