Repository navigation
LiteGate v2.14.0
Highlights
- Migration: Move existing owned keys in place to the primary mapped/default SSO team or deepest hierarchy team, preserving secrets and spend. Retain old memberships/spend for review.
- Safety: Verify inherited allowances and ancestor restrictions; failures retry, with a 500-key per-user bound. Policy-verification errors still require attention.
- Presentation: Leaf-group member usage, six-decimal personal spend and stable
name's keyaliases. Rotation temporarily frees conflicting aliases while the old key remains live until generation succeeds; saved-key reveal is unchanged.
Release Artifacts
Prepared release: versioned artifacts become available after a validated commit
is merged to main, tagged v2.14.0, and the publication workflow succeeds.
| Artifact | Get it |
|---|---|
| Docker image | docker pull ghcr.io/brtydse100/litegate:2.14.0 (after publication)GHCR |
| Live demo | Current demo |
| Docs | Documentation after tagging |
| Source | Source after tagging |
| License | Current MIT license |
Upgrade Notes
- Upgrade chart and image together. Preserve SQLite and the key-storage setting.
- Review team mappings: login/reconciliation now also move keys already assigned to another team.
Changes: #31, #32, #33 by @brtydse100.
Full Changelog: v2.13.0...v2.14.0 (available after tagging)
Contributors
Thanks to @brtydse100 for the changes in this release.