ci: remove helm chart from release please automation

Author: lhoupert

.release-please-manifest.json

@@ -1,4 +1,3 @@
 {
-  ".": "2.0.2",
-  "deployment/k8s/charts": "2.1.2"
+  ".": "2.0.2"
 }

RELEASING.md

@@ -11,24 +11,9 @@ Releases are automated via [release-please](https://github.com/googleapis/releas
    - Updates `CHANGES.md` with the changelog for the new version
 3. When that PR is merged, release-please creates a GitHub release tagged `X.Y.Z`, which triggers the PyPI publish workflow.
 
-## Helm chart releases
+## Helm chart version
 
-The Helm chart (`deployment/k8s/charts/`) is versioned independently from the Python package. release-please opens a separate helm release PR when commits touch files under `deployment/k8s/charts/`. That PR bumps `version:` in `Chart.yaml` and updates `deployment/k8s/charts/CHANGELOG.md`. The resulting GitHub release is tagged `helm-vX.Y.Z`.
-
-**Commit messages matter for chart releases.** A chart version bump only happens when a commit both:
-- touches at least one file under `deployment/k8s/charts/`, **and**
-- uses a bump-triggering type (`fix:`, `feat:`, or a breaking change)
-
-`chore:`, `ci:`, `docs:`, and other non-bumping types that touch chart files are valid conventional commits but will **not** produce a chart release. Use them for housekeeping that doesn't warrant a version bump (e.g. updating CI config, fixing a comment).
-
-Examples:
-
-```
-fix(helm): correct resource limit defaults         → patch bump
-feat(helm): add support for extra environment vars → minor bump
-feat(helm)!: rename required value X to Y         → major bump
-chore(helm): update maintainer list               → no bump
-```
+The Helm chart `version:` in `deployment/k8s/charts/Chart.yaml` is **not** managed by release-please. The chart version is bumped manually when chart structure changes (templates, values, dependencies). The `appVersion` field (the titiler app version the chart deploys) is still updated automatically alongside every Python release, and as part of this process, the chart version can be manually updated by bumping the version in a simple commit in the release please PR.
 
 ## Commit message convention
 
@@ -40,6 +25,6 @@ Version bumps follow [semantic versioning](https://semver.org/) based on commit
 | `feat:` | minor |
 | `feat!:` or `BREAKING CHANGE:` footer | major |
 
-## No manual steps required
+## (Almost) No manual steps required
 
-All version files are updated automatically. Do not manually edit version strings in `pyproject.toml`, `Chart.yaml`, or `__init__.py` files — release-please owns those.
+All version files are updated automatically. Do not manually edit version strings in `pyproject.toml`, `Chart.yaml` (`appVersion`), or `__init__.py` files — release-please owns those. The `version:` field in `Chart.yaml` is the only exception: bump it manually when chart structure changes warrant a new chart release.

release-please-config.json

@@ -41,14 +41,6 @@
         { "type": "generic", "path": "deployment/aws/lambda/Dockerfile" },
         { "type": "generic", "path": "deployment/k8s/charts/Chart.yaml" }
       ]
-    },
-    "deployment/k8s/charts": {
-      "release-type": "helm",
-      "package-name": "titiler-helm",
-      "changelog-path": "deployment/k8s/charts/CHANGELOG.md",
-      "include-component-in-tag": true,
-      "include-v-in-tag": false,
-      "component": "helm"
     }
   }
 }