first commit
This commit is contained in:
89
docs/changelogs/v1.3.19.mdx
Normal file
89
docs/changelogs/v1.3.19.mdx
Normal file
@@ -0,0 +1,89 @@
|
||||
---
|
||||
title: "v1.3.19"
|
||||
description: "v1.3.19 changelog"
|
||||
---
|
||||
<Tabs>
|
||||
<Tab title="NPX">
|
||||
```bash
|
||||
npx -y @maximhq/bifrost --transport-version v1.3.19
|
||||
```
|
||||
</Tab>
|
||||
<Tab title="Docker">
|
||||
```bash
|
||||
docker pull maximhq/bifrost:v1.3.19
|
||||
docker run -p 8080:8080 maximhq/bifrost:v1.3.19
|
||||
```
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
<Update label="Bifrost(HTTP)" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
- chore: allowed changing name when updating a virtual key
|
||||
- feat: add numberOfRetries, fallbackIndex and selected key name and id to context to telemetry metrics
|
||||
- feat: add used virtual key name and id to telemetry metrics
|
||||
- feat: send model deployment back in response extra fields
|
||||
- feat: add selected key and virtual key to logs filter
|
||||
- feat: add headers to MCP client config
|
||||
- feat: add `is_success` label to upstream latency metrics
|
||||
|
||||
</Update>
|
||||
<Update label="Core" description="v1.3.19">
|
||||
|
||||
- feat: add numberOfRetries, fallbackIndex and selected key name to context
|
||||
[BREAKING] changed BifrostContextKeySelectedKey to BifrostContextKeySelectedKeyID
|
||||
- feat: send model deployment back in response extra fields
|
||||
- feat: add headers to MCP client config
|
||||
|
||||
</Update>
|
||||
<Update label="Framework" description="v1.3.19">
|
||||
|
||||
- chore: Upgrades core to 1.2.20
|
||||
- feat: add selected key and virtual key to logs table
|
||||
- feat: add headers to MCP client config
|
||||
|
||||
</Update>
|
||||
<Update label="governance" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="jsonparser" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="logging" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
- feat: add selected key and virtual key to logs
|
||||
|
||||
</Update>
|
||||
<Update label="maxim" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="mocker" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="otel" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="semantic_cache" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
|
||||
</Update>
|
||||
<Update label="telemetry" description="v1.3.19">
|
||||
|
||||
- chore: version update core to 1.2.20 and framework to 1.1.24
|
||||
- feat: add numberOfRetries, fallbackIndex and selected key name and id to context to telemetry metrics
|
||||
- feat: add used virtual key name and id to telemetry metrics
|
||||
- feat: add `is_success` label to upstream latency metrics
|
||||
|
||||
</Update>
|
||||
Reference in New Issue
Block a user