Skip to content

Commit

Permalink
update release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
ishaan-jaff committed Dec 24, 2024
1 parent 1f466ec commit f4a2143
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions docs/my-website/release_notes/v1.55.10/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ import Image from '@theme/IdealImage';

# v1.55.10

`batches`, `guardrails`, `cost tracking`, `logging`
`batches`, `guardrails`, `team management`, `custom auth`


<Image img={require('../../img/batches_cost_tracking.png')} />
Expand All @@ -15,7 +15,20 @@ Track cost, usage for Batch Creation Jobs. [Start here](https://docs.litellm.ai/

Show available guardrails to users. [Start here](https://litellm-api.up.railway.app/#/Guardrails)

##

## ✨ Allow teams to add models

This enables team admins to call their own finetuned models via litellm proxy. [Start here](https://docs.litellm.ai/docs/proxy/team_model_add)


## ✨ Common checks for custom auth

Calling the internal common_checks function in custom auth is now enforced as an enterprise feature. This allows admins to use litellm's default budget/auth checks within their custom auth implementation. [Start here](https://docs.litellm.ai/docs/proxy/virtual_keys#custom-auth)


## ✨ Assigning team admins

Team admins is graduating from beta and moving to our enterprise tier. This allows proxy admins to allow others to manage keys/models for their own teams (useful for projects in production). [Start here](https://docs.litellm.ai/docs/proxy/virtual_keys#restricting-key-generation)



0 comments on commit f4a2143

Please sign in to comment.