You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 93f3273
Browse filesBrowse the repository at this point in the historyBrowse files
* build(deps): core v0.19.4, sdk-go/workcontext v0.1.0, kustomize v0.21.1 (#980)
Core v0.19.4 is additive over v0.19.2 (the issuer's non-consuming
Authority.ReadBack) and holds kustomize at v0.21.1: v0.21.3's kube-openapi
requires structured-merge-diff/v7, which breaks every build compiling
client-go. go.mod LISTED kustomize v0.21.3 and kube-openapi 97fa35140926, and
Go never lowers a listed version, so both are lowered explicitly here; `go mod
graph | grep structured-merge-diff/v7` is now empty.
sdk-go/workcontext moves from its pseudo-version to its first tag, v0.1.0,
which unexports the Verifier alias behind NewVerifier/PinnedVerifier. The CLI
never named it. The matrix declares the v0.19.4 line; supported-matrix.md and
execution-receipts.md stop stating the old pins (the latter also stops citing
TestNoSecondWorkContextImplementation, which no longer exists).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(gitops): admission policies stay cluster-scoped under kyaml v0.21.1 (#980)
kyaml v0.21.1 does not know ValidatingAdmissionPolicy or
ValidatingAdmissionPolicyBinding (v0.21.3 added both as cluster-scoped). With
no answer, kustomize's namespace transformer stamps the overlay's namespace on
them and knownClusterScoped reads them as namespaced, so:
- validateManifest stopped requiring the AppProject's cluster authority for an
admission policy, and snapshotAuthority derived namespaced authority for it;
- validateObjectIdentities no longer indexed them globally, so two
destinations shipping one cluster-wide policy each passed
(TestPromotedTreeRefusesNamespaceFreeObjectsAcrossDestinations went red).
knownClusterScoped falls back to a two-entry table only where kyaml has no
answer, and TestKyamlStillForgetsTheAdmissionPolicyScopes fails once it has
one, so the table is deleted with the next kustomize move. A known
cluster-scoped object is indexed globally whatever namespace a transformer
stamped on it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Antoine Toussaint <312536060+antoinetoussaint-byte@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments