Crossplane v2.3.4

Changes

• !Vulnerability-scannable images (#7574): Container images are now built with buildGoModule (replacing gomod2nix), so published images can be scanned by standard vulnerability tooling.security
• !Dependency security updates: Bumps grpc / golang.org/x/net / golang.org/x/text (#7618, #7614, #7615) and the sigstore stack — cosign (#7559), rekor (#7560), timestamp-authority (#7570), sigstore-go (#7583) — to pick up upstream CVE fixes. See ## What's Changed for the full list.security
• !Update module github.com/sigstore/rekor to v1.5.2 [security] (release-2.3)security
• !Update module github.com/sigstore/cosign/v3 to v3.0.6 [security] (release-2.3)security
• !Update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [security] (release-2.3)security
• !Build with buildGoModule so images are vulnerability-scannablesecurity
• !Update module github.com/sigstore/sigstore-go to v1.2.0 [security] (release-2.3)security
• !Combined security bumps (grpc, x/net, x/text) (release-2.3)security
• !Update module golang.org/x/text to v0.39.0 [security] (release-2.3)security
• !Update module golang.org/x/net to v0.56.0 [security] (release-2.3)security
• +Fixed repeated owner updates for composed Usages (#7597, originally #7591): The Usage controller only checked the first ownerReference when deciding whether the spec.by resource already owned the Usage. A Usage created by a Composition already has the composite as its first owner, so spec.by ended up as a later owner and the controller issued an unnecessary update on every reconciliation — repeatedly re-triggering composition reconciliation and eventually opening the XR circuit breaker. It now checks all owner references.added
• +Crossplane render fixes (#7599, originally #7544): render no longer overwrites the input XR's UID when one is already set, and now validates observed resources before proceeding with the render.added