v0.3.136

fix 'no such directory' error in case of empty kustoimization (#406)

v0.3.135: fix(deps): update node.js to v25.8.0 (#404)

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

v0.3.134

replace ref() by new(); see go 1.26 release notes (#400)

v0.3.133: fix(deps): update non-minor dependencies (#391)

* fix(deps): update non-minor dependencies

* Update generated artifacts

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: ERP4SME-DevOps-GitHub-Workflow-User <134080766+ERP4SME-DevOps-GitHub-Workflow-User@users.noreply.github.com>

v0.3.132: chore(go.mod/go.sum): update dependency go to v1.26.0 (#392)

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

v0.3.131

fix(deps): update module sigs.k8s.io/structured-merge-diff/v6 to v6.3…

v0.3.130: chore(deps): update dependency autoprefixer to v10.4.24 (#384)

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

v0.3.129: fix(major deps): update node.js to v25 (#371)

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

v0.3.128: chore(deps): update dependency go to v1.25.6 (#373)

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

v0.3.127

Fixes/Enhancements

• Clear finalizers when orphaning: the framework protects certain dependent objects (i.e. CustomResourceDefinition and APIService) by adding an own finalizer. Now if such a dependent object is orphaned (e.g. through the delete-policy: orphan annotation), then this finalizer should be removed. Note that this situation might also occur if we render a Helm chart (by HelmGenerator) using helm.sh/resource-policy: keep. This is fixed by this release: from now on, when orphaning objects, our finalizer is cleared from the protected objects.

• Allow to suppress events on dependents: in some cases, the framework does not have permission to create events on the target (e.g. if a kubeconfig or impersonation is used). Now, by setting the annotation

  <operator name>/disable-events: "true"

  on the component, emitting events can be suppressed. In a later phase, we might formalize this annotation into a Configuration interface.

• Enhance scaffolded Helm chart: the chart generated by scaffold now has options to tweak the containedPodDisruptionBudget.