Release flow now points at main but has never run there — prove it before v0.4.0 #116

New issue

Open

opened 2026-08-14 22:09:15 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-08-14 22:09:15 +00:00

Owner

Follow-up to #114. The ported git-cliff automation shipped with on: push: branches: [develop] while its own header comments stated three times that the stable path is automatic on main. Every push to the ungated integration branch therefore cut a public stable release.

Cleaned up on 2026-08-14 (9e53f89): trigger corrected to main, and the five spurious releases v0.3.1–v0.3.5 deleted along with their lightweight tags. v0.3.0 is again the latest release, matching package.json and what production serves.

What that leaves open:

The corrected path is unproven. The workflow has now never fired as designed — main is still a single empty commit, so no release has ever been cut from it. The next real release is also the first live test of the automation.
CHANGELOG.md still opens by citing release-please conventions, and it is .prettierignored, so no gate will ever flag it. Its github.com/BoscoApp/bosco compare links do not resolve either.
The release body template emits emoji banners (🚀, 📊, 🐛), inherited from the tier-kit, against the project's own no-tool-emoji convention. Worth a deliberate decision rather than drift.
main being empty is now load-bearing. With the trigger on main, the release model finally depends on the protected-main convention that Forgejo does not actually enforce (every branch reports protected: false).

Worth doing as one pass before v0.4.0, since v0.4.0 is the first release that would exercise any of it.

Follow-up to #114. The ported git-cliff automation shipped with `on: push: branches: [develop]` while its own header comments stated three times that the stable path is automatic on `main`. Every push to the ungated integration branch therefore cut a public stable release. Cleaned up on 2026-08-14 (`9e53f89`): trigger corrected to `main`, and the five spurious releases `v0.3.1`–`v0.3.5` deleted along with their lightweight tags. `v0.3.0` is again the latest release, matching `package.json` and what production serves. What that leaves open: - **The corrected path is unproven.** The workflow has now never fired as designed — `main` is still a single empty commit, so no release has ever been cut from it. The next real release is also the first live test of the automation. - **`CHANGELOG.md` still opens by citing release-please conventions**, and it is `.prettierignore`d, so no gate will ever flag it. Its `github.com/BoscoApp/bosco` compare links do not resolve either. - **The release body template emits emoji banners** (🚀, 📊, 🐛), inherited from the tier-kit, against the project's own no-tool-emoji convention. Worth a deliberate decision rather than drift. - **`main` being empty is now load-bearing.** With the trigger on `main`, the release model finally depends on the protected-`main` convention that Forgejo does not actually enforce (every branch reports `protected: false`). Worth doing as one pass before v0.4.0, since v0.4.0 is the first release that would exercise any of it.