create new workflow that releases the chart

.github/workflows/publish-charts.yaml

@@ -0,0 +1,30 @@
+name: Publish chart
+
+on:
+  release:
+    types:
+      - released
+
+permissions:
+  contents: write
+
+jobs:
+  release:
+    name: Publish chart to OCI registry
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Helm login
+        run: |
+          echo "${{ secrets.GITHUB_TOKEN }}" | \
+          helm registry login ghcr.io \
+            --username "$GITHUB_REPOSITORY_OWNER" \
+            --password-stdin
+      - name: Helm package
+        run: |
+          helm package charts/stateless-dns -u --version "${GITHUB_REF_NAME#v}"
+      - name: Helm push
+        run: |
+          helm push \
+          "stateless-dns-${GITHUB_REF_NAME#v}.tgz" \
+          "oci://ghcr.io/${GITHUB_REPOSITORY_OWNER}/pdns-stateless"

CHANGELOG.md

@@ -2,6 +2,9 @@
 
 ## Unreleased
 
+### Enhancement
+- Split release process so we can create off-tree emergency releases
+
 ## v0.4.1 - 2024-06-18
 
 ### ⛓️ Dependencies
@@ -11,10 +14,15 @@
 
 ### Note
 All the previous release contain no changelog as it was no automation.
+
 I am solving this with this PR/release/automation that automates the generation of change logs and releases.
+
 I am leveraging this 0ver to do a breaking change. I am changing the URL for this chart from oci://ghcr.io/txqueuelen/charts to oci://ghcr.io/txqueuelen/pdns-stateless.
+
 It seemed that is awesome to have all charts on the same path and loved that Github supported it but I found that is hard to follow the origin of a chart. Users expect to have the chart in a repository called `charts`.
+
 This breaking change should not affect too much as almost no user is using this release note is a way of documenting the changes.
+
 Luckily there are only a few 0ver releases from here once we merge all dependencies that need to be upgraded and make the last changes before creating the v1 release :D
 
 ### 🚀 Enhancements