mirror of
https://github.com/BerriAI/litellm.git
synced 2026-11-11 08:38:24 +00:00
84617874b8
* fix(ui): resolve auto router templates through ids a * catch-all lists over a partial wildcard * fix(ui): resolve wildcard-listed ids by their routed model in the Simple view and named aliases A catch-all's fixed model or base_model no longer keys every listed id as that one model, a named alias like claude/* over anthropic/claude-* keys its ids by the model the router sends them to, and the Simple view suggests a pair from those ids too * fix(ui): credit a wildcard-listed id only through the pattern and provider the router uses When several named wildcards match a listed id, only the one the router's specificity sort picks is credited. A captured route counts only when its provider is one /model_group/info reports for the group, so an alias that points elsewhere keeps its own name. Paused catch-alls credit nothing, and a name with its own text before the star captures like the proxy lists it. * fix(ui): resolve model group aliases before wildcards in auto router templates An alias that shadows an id the catch-all lists now counts as the model the router sends it to, and paused deployments credit no template model * fix(ui): wait for aliases, read them as admin only, and skip paused wildcard routes in auto router templates * fix(ui): let slashless wildcard model names take part in route precedence The router puts every model_name holding a star into its pattern list, with or without a slash, so a listed id like opus-5-5 under a "*" catch-all goes to a more specific opus-* deployment first. The dashboard skipped slashless names when it picked the route, so a paused opus-* still credited opus-5-5 through the catch-all and a template could fill a tier that answers 403. The old "derives no pattern from a slashless wildcard model_name" test described /models listing, not routing, and is replaced by the routed case. --------- Co-authored-by: mateo-berri <277851410+mateo-berri@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .agents/skills/url-state | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| vendor | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| 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.production.json | ||
| 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.