Skip to content

LiteGate v2.13.0

Choose a tag to compare

@github-actions github-actions released this 15 Oct 05:38
· 32 commits to main since this release
069f8f0

Artifacts

Artifact Get it
Docker image docker pull ghcr.io/brtydse100/litegate:2.13.0
GHCR
Live demo Current demo
Docs Documentation
Source GitHub
License MIT

Warning

Helm upgrade required for organization hierarchy
Use the Helm chart from the LiteGate v2.13.0 source tag together with
application image 2.13.0. Changing only image.tag does not add the hierarchy
configuration or automatic rollout support. Hierarchy management remains
disabled by default.

What's Changed

  • Add organization hierarchy and lowest-team key allowances by @brtydse100 in #25

  • Show current policy values and safely migrate individual key budgets by @brtydse100 in #26

  • Cover concurrent key regeneration and preserved spending by @brtydse100 in #27

  • Unify personal API key display and show-hide controls by @brtydse100 in #28

  • Add isolated LiteLLM and OpenRouter budget testing helpers by @brtydse100 in #29

  • release: prepare v2.13.0 by @brtydse100 in #30

Organization budgets and upgrade notes

  • organizationHierarchy.levels: [] keeps hierarchy management disabled by
    default. Enable up to eight configured levels through Helm or Compose YAML.
    Back up the existing LiteGate SQLite database and LiteLLM policies before
    enabling reconciliation; update the application image and Helm chart together.
  • Each group owns a real LiteLLM team. A user's key belongs to the deepest
    matching group. The compatibility-named perUser setting supplies the
    inherited per-key allowance; it is not a second personal user budget.
  • Parent groupTotal values are tracking targets only. Organization reports
    sum native descendant team spend; ancestor targets do not block requests.
    Native Teams spend remains attributed to the key's actual owning team.
  • Reconciliation verifies key ownership and allowances before removing duplicate
    personal/member caps or obsolete shared caps. Unknown or unprotected
    credentials keep their old caps. Conflicting memberships and policy-losing
    migrations fail with a synchronization warning.
  • LiteLLM needs a database and its key/team management APIs. Daily analytics
    also depend on the deployed LiteLLM version and license. Detailed reports
    attribute historical usage using current membership.

See Organization hierarchy and
configuration for examples, inheritance and safeguards.

Policy editing and key safety

  • Key and team editors show saved values and retain saved model names. Bulk key
    edits submit only changed fields. Model checkboxes and numeric controls follow the
    selected theme. Key settings appear after selection; managed teams are tagged.
  • An explicit administrator action can migrate an unmanaged owner's sole finite
    key allowance away from duplicate personal and team-member caps. Shared team
    budgets remain in force; unsupported verification returns an item-level error.
  • Regeneration retains recorded spend and a known finite unmanaged key budget
    and reset interval. Migration, rotation and personal portal deletion share the owner lock.
    An unverifiable replacement is revoked before the old key is deleted.
  • Created and revealed personal keys share a compact green panel, copy icon and
    full-width Show/Hide control. Optional stored secrets still require authorized
    reveal requests and stay in component memory in the browser. Secret storage
    remains disabled by default. Sub-cent spend remains visible in reports.

Local testing

The testing guide includes isolated
LiteLLM/LiteGate startup, free OpenRouter model registration, and a request script.
Provider credentials are entered locally. High and cheap model prices are
artificial local accounting rates for budget tests, separate from provider cost.

Full Changelog: v2.12.2...v2.13.0

Contributors

Thanks to @brtydse100.