MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 100 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

feat: MokoGitea update checker system #74

New Issue
Closed
opened 2026-05-13 00:12:56 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-13 00:12:56 +00:00
Owner
Copy Link
Copy Source

Summary

Build a MokoGitea-native update checker to replace the removed upstream Gitea update checker. The upstream checker has been removed from the codebase as part of the fork separation (it pointed to dl.gitea.com/gitea/version.json and would show misleading "update available" banners for upstream Gitea releases).

Requirements

  • Create a version endpoint on git.mokoconsulting.tech that serves MokoGitea release versions
  • Implement modules/updatechecker/ with MokoGitea-specific version checking against our own endpoint
  • Register as a cron task in services/cron/tasks_extended.go
  • Show update banner on admin dashboard when a new MokoGitea version is available
  • Version comparison should use MokoGitea versioning scheme (e.g. v1261.0.0)
  • Endpoint should be configurable via app.ini ([cron.update_checker] section)

Context

  • The upstream modules/updatechecker/update_checker.go was removed along with its cron registration, install form checkbox, and admin dashboard banner
  • MokoGitea uses its own versioning independent of upstream Gitea
  • The version endpoint should be self-hosted on our MokoGitea instance

Related Work

  • Upstream Gitea references (docs.gitea.com, about.gitea.com) are being replaced throughout the codebase as part of the fork separation
  • Dot-repo privacy enforcement feature is also planned

Authored-by: Moko Consulting

## Summary Build a MokoGitea-native update checker to replace the removed upstream Gitea update checker. The upstream checker has been removed from the codebase as part of the fork separation (it pointed to `dl.gitea.com/gitea/version.json` and would show misleading "update available" banners for upstream Gitea releases). ## Requirements - [ ] Create a version endpoint on `git.mokoconsulting.tech` that serves MokoGitea release versions - [ ] Implement `modules/updatechecker/` with MokoGitea-specific version checking against our own endpoint - [ ] Register as a cron task in `services/cron/tasks_extended.go` - [ ] Show update banner on admin dashboard when a new MokoGitea version is available - [ ] Version comparison should use MokoGitea versioning scheme (e.g. `v1261.0.0`) - [ ] Endpoint should be configurable via `app.ini` (`[cron.update_checker]` section) ## Context - The upstream `modules/updatechecker/update_checker.go` was removed along with its cron registration, install form checkbox, and admin dashboard banner - MokoGitea uses its own versioning independent of upstream Gitea - The version endpoint should be self-hosted on our MokoGitea instance ## Related Work - Upstream Gitea references (`docs.gitea.com`, `about.gitea.com`) are being replaced throughout the codebase as part of the fork separation - Dot-repo privacy enforcement feature is also planned --- *Authored-by: Moko Consulting*
jmiller commented 2026-05-21 01:43:28 +00:00
Author
Owner
Copy Link
Copy Source

Verified on v1.26.1-moko.3

Implementation

  • Cron task registered: runs at startup + every 24h
  • Checks git.mokoconsulting.tech releases API
  • Compares semver to running version
  • Shows banner in admin dashboard when update available

Config

[update_checker]
ENABLED = true
ENDPOINT = https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoGitea/releases/latest

Authored-by: Claude Opus 4.6 (1M context)

## Verified on v1.26.1-moko.3 ### Implementation - Cron task registered: runs at startup + every 24h - Checks git.mokoconsulting.tech releases API - Compares semver to running version - Shows banner in admin dashboard when update available ### Config ```ini [update_checker] ENABLED = true ENDPOINT = https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoGitea/releases/latest ``` *Authored-by: Claude Opus 4.6 (1M context)*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#74
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?