mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-05 02:41:56 +00:00
774444fcd7
Some checks failed
LiteLLM Rust / rustfmt, clippy, test (push) Has been cancelled
Terraform Modules / fmt, validate, test (aws) (push) Has been cancelled
Terraform Provider / gofmt, vet, build, test (push) Has been cancelled
Terraform Provider / Provider endpoints vs proxy OpenAPI schema (push) Has been cancelled
Team member permission writes previously accepted every
KeyManagementRoutes value (and /team/permissions_update accepted any
string at all), but only nine of those grants are ever read by the
permission checks; values like /key/block or /key/bulk_update guard
admin-only endpoints and the templated /key/{key_id}/... entries are
enforced under their plain counterparts, so granting them silently did
nothing. A new TeamMemberPermissions enum narrows the write surfaces
(default team settings, /team/permissions_update,
/team/permissions_bulk_update) to the nine enforced grants plus the
always-included /key/info and /key/health, /team/permissions_list now
advertises only the nine grantable values, and the default team
settings form derives its checkboxes from the new enum
BREAKING CHANGE: PATCH /update/default_team_settings,
POST /team/permissions_update, POST /team/permissions_bulk_update, and
litellm_settings.default_team_params now reject team member permission
values that were never enforced: /key/block, /key/unblock,
/key/bulk_update, /team/key/bulk_update, /key/{key_id}/regenerate,
/key/{key_id}/reset_spend, /key/aliases, /spend/logs/v2. Stored values
are unaffected and still read back
|
||
|---|---|---|
| .. | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| CLAUDE.md | ||
| components.json | ||
| eslint-budgets.json | ||
| eslint-suppressions.json | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.tsbuildinfo | ||
| vitest.config.ts | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.