MokoConsulting/MokoGIT
1
0
Fork 0
Code Issues 161 Pull Requests 3 Releases 96 Wiki Activity

updates.xml must not emit a Joomla feed for npm/mcp; fix empty-platform => joomla fallback #810

New Issue
Closed
opened 2026-07-18 19:54:36 +00:00 by jmiller · 0 comments
jmiller commented 2026-07-18 19:54:36 +00:00
Owner
Copy Link
Copy Source

ServeUpdatesXML treats an unset update-stream Platform as joomla, so an npm/mcp repo that ever cut a release would emit a meaningless Joomla feed. Add npm/mcp as recognized update-stream Platform values routed to NotFound/N-A, and remove the empty=>joomla default. Evidence: mcp repos return HTTP 200 empty <updates> today only because they have zero releases.

Part of the MokoGIT release-system redesign (all-platforms assessment, 2026-07-18). Hybrid direction: server-side packaging, build/publish stay on runners.
Authored-by: Moko Consulting

`ServeUpdatesXML` treats an unset update-stream Platform as joomla, so an npm/mcp repo that ever cut a release would emit a meaningless Joomla feed. Add `npm`/`mcp` as recognized update-stream Platform values routed to NotFound/N-A, and remove the empty=>joomla default. Evidence: mcp repos return HTTP 200 empty `<updates>` today only because they have zero releases. --- Part of the MokoGIT release-system redesign (all-platforms assessment, 2026-07-18). Hybrid direction: server-side packaging, build/publish stay on runners. Authored-by: Moko Consulting
jmiller added the securityci-cd labels 2026-07-18 19:54:36 +00:00
Sign in to join this conversation.
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
 feature: wiki
Wiki system enhancements
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 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
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels ci-cd security
Priority Medium
Type Feature
Milestone
No items
No Milestone
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/MokoGIT#810
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?