chore: release 0.14.0

[flant-team-sysdev]

🤖 I have created a release *beep* *boop*

0.14.0 (2026-02-17)

Features

• crs: add tracking rules for new custom resources (2491f12)
• greatly decrease Kubernetes apiserver load (40930a9)
• kube: add support for kube token (#387) (d2aee7a)
• rules: add rule for bitnami sealed secrets (6948d26)
• rules: add rules for kyverno policy and cluster policy (#361) (9511e8d)
• rules: add tracking rules for longhorn resources (#374) (f394e96)
• rules: add tracking rules for prometheus resources (#373) (b80f0b6)
• SaveLogsOnlyForNumberOfContainers option (d16322b)
• tracker: pass DynamicReadinessTrackerOptions.IgnoreLogs option down to pod tracker (94b0a93)

Bug Fixes

• add standalone pod tracking (119a05f)
• allow generic tracker static rules for empty string values (7c68c9c)
• consider init container error on tracking (5da2812)
• disable potentially problematic resource tracking rules (a3c45a7)
• docker hub creds might leak in pod events (25b3a13)
• error not returned if context canceled (6ffc5a1)
• external secrets readying if external secret has no status (cd33f46)
• fix false positive (#370) (88394a2)
• improve context cancellation handling and logging (0ea6140)
• kube: correctly resolve client config per context (#388) (5d3f8c0)
• leaking goroutines in dynamic tracker (78ba12f)
• no logs collected (d5883c1)
• panic "validate rules file" (acff6da)
• panic if apiserver connection lost (6356856)
• retry logs streaming after 3.5 hours to workaround 4h kubelet limit (c7a4f0b)

---

This PR was generated with Release Please. See documentation.

[vaivanov]

Hello! I was planning to add a feature to your tool, but after building this release I’m seeing runtime errors. I also noticed this release has been waiting to be published for about six months. Could you share your plans - are you planning to fix and publish it?

[ilya-lesikov]

Hello, the plan right now is to make a Go library out of kubedog, without cli. Kubedog release 1.0 will only have this new public API left, cli will be removed too. We are focusing on Kubedog integration into Nelm and werf, a standalone Kubedog cli on top of everything else is just too much for us. Someone did their own cli for kubedog, can't find it, I believe it was somewhere in the issues.

All of this CI and release process need to be remade too. We just started working on werf 3.0, nelm 2.0 and kubedog 1.0 releases, it will probably take half a year.