chore(deps): bump docker/build-push-action from 6.19.2 to 7.0.0#1
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
chore(deps): bump docker/build-push-action from 6.19.2 to 7.0.0#1dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
bot
added
dependencies
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.19.2 to 7.0.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@10e90e3...d08e5c3) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/github_actions/docker/build-push-action-7.0.0
branch
from
4a68ded to
e8cdba9
Compare
Contributor
Author
|
Looks like docker/build-push-action is up-to-date now, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/github_actions/docker/build-push-action-7.0.0
branch
christianromeni
added a commit
that referenced
this pull request
Mar 25, 2026
Adds multi-deployment support per model with automatic routing, failover, and retry logic. The #1 feature gap vs LiteLLM. Config: models can define a `deployments` list with per-endpoint provider, base_url, api_key, weight, and priority. Backward compatible — existing single-deployment configs work unchanged. Routing strategies: round-robin (default), least-latency, weighted, priority. Router filters by health status and circuit breaker state. All deployments unhealthy → tries all as last resort. Retry: on 5xx/timeout/connection error, automatically tries the next deployment. 4xx errors return immediately. No retry after streaming starts. Per-deployment circuit breakers with independent cooldowns. New: internal/router package, internal/db/deployments CRUD, model_deployments table (migration 0003), Admin API deployment endpoints, per-deployment health probing, routing retry metrics. Community feature — no license gating.
9 tasks
christianromeni
added a commit
that referenced
this pull request
Mar 26, 2026
* feat: multi-deployment load balancing with fallbacks Adds multi-deployment support per model with automatic routing, failover, and retry logic. The #1 feature gap vs LiteLLM. Config: models can define a `deployments` list with per-endpoint provider, base_url, api_key, weight, and priority. Backward compatible — existing single-deployment configs work unchanged. Routing strategies: round-robin (default), least-latency, weighted, priority. Router filters by health status and circuit breaker state. All deployments unhealthy → tries all as last resort. Retry: on 5xx/timeout/connection error, automatically tries the next deployment. 4xx errors return immediately. No retry after streaming starts. Per-deployment circuit breakers with independent cooldowns. New: internal/router package, internal/db/deployments CRUD, model_deployments table (migration 0003), Admin API deployment endpoints, per-deployment health probing, routing retry metrics. Community feature — no license gating. * feat: expandable deployment rows in Models page - Table component: generic renderExpandedRow/expandedKeys/onToggleExpand - Models page: multi-deployment models show expand chevron, deployment count + strategy badge, aggregated health status - Expanded view: sub-table with own headers (Deployment, Provider, Health, Base URL, Weight, Priority) per deployment - Health aggregation: all unhealthy→unhealthy, all healthy→healthy, all unknown→unknown, mix→degraded - ListModels: batch-fetch deployments (single query instead of N+1) - ListDeploymentsByModelIDs: new batch DB method * feat: deployment management UI + tests + docs UI: - Create Model dialog: mode switch (Single Endpoint / Load Balanced) - Load Balanced mode: strategy selector, inline deployment list with add/edit/remove, creates model then deployments sequentially - DeploymentDialog: shared create/edit dialog for individual deployments - Expanded row: edit/delete buttons per deployment, add deployment button — only for API-sourced models (YAML is read-only) Backend: - Provider/base_url no longer required when model has strategy set Tests: - 11 DB deployment tests (CRUD, batch fetch, soft delete, conflicts) - 14 API deployment tests (CRUD, validation, IDOR checks, key redaction) Docs: - Load Balancing section in configuration.md with strategies, retry behavior, health integration, and circuit breaker explanation * fix: dialog scroll + UI polish for deployment management - Dialog: max-h-[90vh] with scrollable content, thin scrollbar - Dialog: slightly wider (max-w-xl) - Create Model: advanced settings (pricing, context, timeout) behind collapsible to reduce dialog height - Expand chevron only shown for models with deployments - Add deployment "+" button only for load-balanced API models - No deployment actions on YAML-sourced models
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps docker/build-push-action from 6.19.2 to 7.0.0.
Release notes
Sourced from docker/build-push-action's releases.
Commits
d08e5c3Merge pull request #1479 from docker/dependabot/npm_and_yarn/docker/actions-t...cbd2dffchore: update generated contentf76f51fchore(deps): Bump@docker/actions-toolkitfrom 0.78.0 to 0.79.07d03e66Merge pull request #1473 from crazy-max/rm-deprecated-envs98f853dchore: update generated contentcadccf6remove deprecated envs03fe877Merge pull request #1478 from docker/dependabot/github_actions/docker/setup-b...827e366chore(deps): Bump docker/setup-buildx-action from 3 to 4e25db87Merge pull request #1474 from crazy-max/rm-export-build-tool1ac2573Merge pull request #1470 from crazy-max/node24Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)