v0.3.66

fix(deps): update module sigs.k8s.io/controller-runtime to v0.20.1 (#…

v0.3.65: add template functions (must)lookupWithKubeConfig (#181)

* add template functions (must)lookupWithKubeConfig

* change kubeconfig type from []byte to string

v0.3.64

update CONTRIBUTING

v0.3.63: fix(go.mod/go.sum): update module golang.org/x/time to v0.9.0 (#196)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

v0.3.62

Incompatible changes

Previously, the forced re-apply of dependent objects was based on a timestamp that was coded into the object digest. As a consequence, the digest annotation of every dependent object was updated more or less every 60 minutes. Which caused problems (e.g. with crossplane).

From this release onwards, the force-re-apply mechanism is based on the new status field status.inventory[].lastAppliedAt.

Note: YOU MUST, REALLY MUST, regenerate your component CRD when using a version of component-operator-runtime containing this release, and ship the module update together with the updated CRD!!!

v0.3.61

fix code comment

v0.3.60: fix(deps): update node.js to v23.5.0 (#191)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

v0.3.59

This release is non-functional (preparation for future work). It ships a new status field .status.inventory[].lastAppliedAt.

v0.3.58

This release is a bugfix release for the clm cli. So far, while applying or deleting a release, clm was aborting immediately if an error occurred. This is not very convenient. At least in some ephemeral error situations, it should behave in a more resilient way. So, with this release, clm tries to recognise such ephemeral errors (for example 409 - Conflict responses from the API server), and retries the failing operation a couple of times.

v0.3.57

workflows: disable cgo