Skip to content

fix: vault reads, default environment, and 0.23.3 - #151

Merged
BRAVO68WEB merged 2 commits into
mainfrom
fix/vault-reads-and-default-env
Oct 6, 2026
Merged

BRAVO68WEB merged 2 commits into
mainfrom
fix/vault-reads-and-default-env

Conversation

@BRAVO68WEB

Copy link
Copy Markdown
Contributor

Summary

  • Pin miniKMS to ghcr.io/envsync-cloud/minikms:sha-4280c5e (PR Redesign of landing page #13 is already on GHCR). API traces now record the gRPC operation, org, scope, entry type, and key name, plus the status code when the call fails.
  • A vault read failure no longer hides a recreated env var or secret from GET. The list keeps the point-in-time value, and changes in one batch are ordered a millisecond apart.
  • Creating an app always adds a default Development environment, so the dashboard does not crash when no environment types were entered.
  • Patch release 0.23.3. Tag v0.23.3 after this merges.

Test plan

  • miniKMS TestToStatusError and TestVaultRead on the image commit
  • CI
  • Create a project with no environments and open Variables
  • Delete an env var, recreate it with the same name, and confirm GET returns it

Pin miniKMS to ghcr.io/envsync-cloud/minikms:sha-4280c5e. Record gRPC
operation details on API traces, keep a point-in-time value when a
vault read fails, and create a Development environment with each app.
@BRAVO68WEB
BRAVO68WEB merged commit ed7338c into main Oct 6, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant