[major] Harden the Vault proxy boundary#10
Merged
Conversation
libops-agent
force-pushed
the
secure-vault-proxy-v2
branch
2 times, most recently
from
July 15, 2026 18:52
84a3df0 to
162f869
Compare
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
libops-agent
force-pushed
the
secure-vault-proxy-v2
branch
from
July 15, 2026 18:57
162f869 to
1ce54fb
Compare
libops-agent
marked this pull request as ready for review
July 15, 2026 19:02
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.
Summary
Validation
go test -race ./...go mod tidy -diffactionlint .github/workflows/*.yamlDependency
This release must land before the API Vault module starts emitting version-2 route patterns.