ZDDC 360601e262 fix(ci): chart MINOR-bump on stable cut (resets PATCH to 0) ... Chart version was monotonically incrementing PATCH on every chart-bump — after ~50 betas + a few stable cuts, version was already at 0.2.12. Triple digits would land within a year of active dev. Switch the stable-cut branch of notify-chart-bump.sh to bump MINOR and reset PATCH to 0: stable: 0.2.X → 0.3.0 beta: 0.3.0 → 0.3.1, 0.3.1 → 0.3.2, ... next stable: 0.3.X → 0.4.0 Patches stay bounded (≈ betas-per-stable, not all-time). MINOR keeps incrementing so JFrog chart-repo uploads stay accepted (it rejects duplicate chart-version numbers — a literal "reset to 0.2.0" cycle would break uploads on the second stable cut). Chart version is purely JFrog packaging metadata; the zddc-server version users actually care about lives in appVersion.		2026-05-04 07:49:17 -05:00
..
scripts	fix(ci): chart MINOR-bump on stable cut (resets PATCH to 0)	2026-05-04 07:49:17 -05:00
workflows	refactor(ci): extract chart-bump logic to .forgejo/scripts/	2026-05-04 07:49:16 -05:00