rc(v05.01.00): update checker channels + SHA256 release checksums #176

Merged

jmiller merged 11 commits from rc/05.01.00 into main 2026-05-26 00:28:14 +00:00

Conversation 0 Commits 11 Files Changed 10

+323 -46

11 Commits

Author	SHA1	Message	Date
jmiller	64e1e37e20	Merge pull request 'fix: generate checksums on API asset upload' (#175) from feat/release-sha-checksums into dev	2026-05-26 00:15:52 +00:00
Jonathan Miller	a847129f9c	fix: generate checksums on API asset upload, not just CreateRelease ... The API endpoint POST /releases/{id}/assets bypasses CreateRelease and UpdateRelease, so checksums were not generated for API uploads. Added GenerateReleaseChecksums call after successful asset upload. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 19:15:12 -05:00
jmiller	30e16cccc1	Merge pull request 'feat: auto-generate SHA256 checksums for release attachments' (#174) from feat/release-sha-checksums into dev	2026-05-26 00:08:48 +00:00
jmiller	b74cf800ef	Merge pull request 'feat: update checker channels, email + ntfy notifications' (#173) from feat/update-checker-channels into dev	2026-05-26 00:08:09 +00:00
Jonathan Miller	90f612f211	feat: auto-generate SHA256 checksums for release attachments ... When a release is created or updated with attachments, automatically compute SHA256 checksums for every file and attach a checksums.sha256 manifest file. The manifest follows the standard sha256sum format: <hash> <filename> Existing checksums.sha256 files are replaced when attachments change. Checksums are generated for both CreateRelease and UpdateRelease flows. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 19:05:13 -05:00
Jonathan Miller	49fe3cf6eb	feat: add ntfy push notification for update checker ... Update notifications now go through three channels: - Admin dashboard banner (existing) - Email to admin (added in previous commit) - ntfy push notification (new) Configure in app.ini: [ntfy] ENABLED = true SERVER_URL = https://ntfy.mokoconsulting.tech DEFAULT_TOPIC = mokogitea TOKEN = (optional bearer token) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 18:34:14 -05:00
Jonathan Miller	13352e7213	feat: email admin when MokoGitea update is detected ... The update checker now emails the first admin user when a new version is found on the configured channel. Notifications are deduplicated — only sent once per new version, not on every cron tick. - Added NotifyFunc callback in updatechecker module - Wired to mailer in cron task registration - Created mail_update.go with plain-text email including version, channel, release URL, and docker pull command Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 18:24:03 -05:00
Jonathan Miller	07827bcc2e	test: bump dev channel to 06.00.00-dev to test update checker ... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 18:19:32 -05:00
Jonathan Miller	8509932b41	feat: update channel selector dropdown on admin dashboard ... Add a dropdown on the admin dashboard to switch between update streams (stable, rc, beta, alpha, development) matching the Joomla pattern. Changes: - Admin dashboard shows channel selector with descriptions - POST handler validates and applies channel change in-memory - Triggers immediate re-check against updates.xml after switch - updates.xml has all 5 standard channels with descriptions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 17:58:39 -05:00
Jonathan Miller	8ad1b8a110	chore: align update streams to standard channels (dev/alpha/beta/rc/stable) ... Matches the Joomla update server pattern used across all Moko repos. Removed the non-standard 'security' channel. All five standard channels now present in updates.xml. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 17:55:28 -05:00
Jonathan Miller	be5c2d35a5	chore: bump updates.xml to v05.00.00 ... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 17:53:13 -05:00