ZDDC 1033d30ad9 fix(ci): notify-chart workflows push to Forgejo, not GitHub ... The chart repo (BMCD/tnd-zddc-chart) is mirrored Forgejo→GitHub one-way (we set this up so the chart matches the same canonical- on-Forgejo pattern as the public repos). When notify-chart-prod and notify-chart-dev pushed directly to GitHub, the bump landed on GitHub but Forgejo never got it — and the next time Forgejo's push-mirror ran, it force-overwrote GitHub's bump with Forgejo's older state. Symptom: prod stuck at v0.0.9 even after auto-bump appeared to succeed; manual investigation showed Chart.yaml appVersion was actually still 0.0.10 (the previous manual bump that DID land on Forgejo). Fix: clone+push to Forgejo (git.varasys.io/BMCD/tnd-zddc-chart) instead of GitHub. Forgejo's mirror replicates to GitHub on the next sync — going through the canonical-Forgejo path keeps both sides in sync. Uses a new CHART_FORGEJO_TOKEN secret (separate from CHART_GITHUB_TOKEN, which is no longer needed for these workflows but kept for any future direct-GitHub use case).		2026-05-03 19:39:48 -05:00
..
workflows	fix(ci): notify-chart workflows push to Forgejo, not GitHub	2026-05-03 19:39:48 -05:00