BACKLOG: claim DC-034 (regenerate release tarball as 1.14.9)

2026-07-05 22:01:32 -07:00
parent 47970cfd14
commit be25c598f1
1 changed files with 2 additions and 2 deletions
@@ -159,8 +159,8 @@
 ## P1 — Code Quality

 ### DC-034: Regenerate get.dashcaddy.net/release tarball as v1.14.9 with DC-033 baked in
- **status:** todo
- **owner:** unclaimed
+- **status:** in-progress
+- **owner:** krystie
 - **details:** Live `https://get.dashcaddy.net/release/version.json` advertises v1.14.8 (commit `ba23cdf`) but DC-033 is NOT in that tarball — verified by extracting `dashcaddy/dashcaddy-api/src/docker/self-updater.js` from `dashcaddy-1.14.8.tar.gz` and confirming it still has the broken `__dirname` pattern. Every other DashCaddy host that auto-updates to v1.14.8 will hit the same 0.0.0 dashboard bug DNS2 just had. Fix: (1) bump `package.json` to `1.14.9` + update `dashcaddy-api/VERSION` to the DC-033 commit SHA. (2) populate `[Unreleased]` section in CHANGELOG.md with DC-033 entry. (3) run `bash scripts/publish-release.sh` to rebuild + push the tarball to get.dashcaddy.net. (4) verify the live `version.json` reflects the new version + commit. Effort: ~15 min. Risk: low — release pipeline already proven by build-pipeline-fix.
 - **impact:** Every host auto-updating gets the 0.0.0 fix for free without needing a manual symlink or git pull.