v0.4.0

What's Changed

• Use distroless/static image instead of distroless/base since glibc is not used by @vilmosmartinek in #49
• Update module github.com/crossplane/function-sdk-go to v0.4.0 by @renovate in #50

New Contributors

• @vilmosmartinek made their first contribution in #49

Full Changelog: v0.3.0...v0.4.0

v0.3.0

This release updates the function to use the new v1 function RPCs introduced with Crossplane v1.17.

This version is backward compatible with Crossplane v1.16 and earlier, that use v1beta1 function RPCs.

You can install this release using the following manifest:

apiVersion: pkg.crossplane.io/v1
kind: Function
metadata:
  name: function-auto-ready
spec:
  package: xpkg.upbound.io/crossplane-contrib/function-auto-ready:v0.3.0

What's Changed

• Add package metadata by @negz in #14
• Update actions/setup-go action to v5 by @renovate in #18
• Update module google.golang.org/protobuf to v1.34.2 by @renovate in #21
• Update golangci/golangci-lint-action action to v6 by @renovate in #30
• Update docker/build-push-action action to v6 by @renovate in #31
• Update module github.com/alecthomas/kong to v0.9.0 by @renovate in #26
• Update module github.com/alecthomas/kong to v1 by @renovate in #37
• Bump function-sdk-go to v0.3.0 by @negz in #38

Full Changelog: v0.2.1...v0.3.0

v0.2.1

This release only adds package metadata annotations it is functionally identical to v0.2.0.

You can install this release using the following manifest:

apiVersion: pkg.crossplane.io/v1beta1
kind: Function
metadata:
  name: function-auto-ready
spec:
  package: xpkg.upbound.io/crossplane-contrib/function-auto-ready:v0.2.1

v0.2.0

The first release of function-auto-ready 🎉 ¹

This composition function automatically detects composed resources that are ready. See the README for more details.

You can install this function using the following manifest:

apiVersion: pkg.crossplane.io/v1beta1
kind: Function
metadata:
  name: function-auto-ready
spec:
  package: xpkg.upbound.io/crossplane-contrib/function-auto-ready:v0.2.0

1. We used v0.1.x during development, so we're releasing at 0.2.0. ↩