Repository navigation
chore(no-release): pin validators and clarify GitOps ownership - #29
Merged
justgithubaccount merged 1 commit intoOct 30, 2026
Merged
Conversation
justgithubaccount
marked this pull request as ready for review
October 30, 2026 14:04
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 30, 2026
## [1.5.1](v1.5.0...v1.5.1) (2026-10-30) ### 🐛 Bug Fixes * **gitops:** keep supported roots version-pinned ([#30](#30)) ([a710ef8](a710ef8)) * **no-release:** validate every rendered resource with OPA ([8f4f312](8f4f312)) ### 📚 Documentation * **no-release:** modernize Kubernetes repository documentation ([ab2f722](ab2f722)) ### 🏗️ Chores * **no-release:** clarify GitOps ownership and validation ([2033b80](2033b80)) * **no-release:** clean configuration comments ([5bc380b](5bc380b)) * **no-release:** pin validators and clarify GitOps ownership ([#29](#29)) ([0925bc5](0925bc5))
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.
Scope
Final audit #27 / infra #31 K8s/GitOps pass: exact OPA 1.22.0 and kubeconform 0.8.0 downloads with upstream checksum verification, a no-moving-download regression contract, and a fail-closed ownership ledger covering roots, ApplicationSets, projects and optional data/platform resources.
No Rego policy or Kubernetes manifest changed.
Validation
Exact head c4fc8d0. Dev render before/after SHA-256 e97f127ba4893e3f1e3650f9990621394179cceb59934b28dc059221e03f6b2c; smoke 479edc2b4fc4e90477ac0001a6ced7045c4b268824686c9a6ca66f520f410312. Ownership/networking/OPA multi-document/contracts, OPA policy/render validation, kubeconform (0 invalid) and critical release audit gate PASS.
Exact-head Actions run 41065698398 PASS: contracts 124096376867, render dev 124096377278, render smoke 124096377755.
Residual npm is only the semantic-release bundled npm executable: ip-address moderate (one GHSA) and undici high (five GHSA); no compatible npm 11 fix exists. It is not deployed Kubernetes payload. The critical-only gate remains accurately documented.
No merge, release, deployment, Argo sync or Kubernetes operation is authorized.