Crossplane v2.1.8

v2.1.8
Fixed 1
  • Usage controller now checks all owner references instead of only the first one, preventing repeated owner updates for composed Usages and unnecessary composition reconciliation triggering
Security 7
  • Bump Go toolchain to 1.25.12 to pick up upstream CVE fixes
  • Update github.com/sigstore/rekor to v1.5.2 for security fixes
  • Update github.com/sigstore/timestamp-authority to v2.1.0 for security fixes
  • Update github.com/sigstore/cosign to v2.6.3 for security fixes
  • Update github.com/sigstore/sigstore-go to v1.2.0 for security fixes
  • Update grpc, golang.org/x/net, and golang.org/x/text for security fixes
  • Update golang.org/x/text to v0.39.0 for security fixes

v2.1.8 is a patch release scoped to fixing issues reported by users of Crossplane v2.1 and fixing security related issues in Crossplane's dependencies.

🎉 Highlights

  • Fixed repeated owner updates for composed Usages (#7622, 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.
  • Dependency security updates: Bumps the Go toolchain to 1.25.12 (#7577), grpc / golang.org/x/net / golang.org/x/text (#7620, #7609), and the sigstore stack — cosign (#7556), rekor (#7555), timestamp-authority (#7568), sigstore-go (#7581) — to pick up upstream CVE fixes. See ## What's Changed for the full list.
What's Changed

Full Changelog: https://github.com/crossplane/crossplane/compare/v2.1.7...v2.1.8

View original

Upgraded? How did it go?

Discussion