deploy: update-server registry adoption + #811 feedless-platform feed precedence #831

Merged

jmiller merged 3 commits from dev into main 2026-07-19 06:42:47 +00:00

Conversation 0 Commits 3 Files Changed 2

+97 -40

jmiller commented 2026-07-19 06:12:45 +00:00

Owner

Copy Link

Copy Source

Promotes #830 to main (triggers deploy-prod). Ships ONLY #811: feedless metadata platforms (npm/mcp/go, feed_format==none) return N/A from their update feed even over a legacy default-joomla update_stream_config row. Genuine Joomla repos unaffected (metadata.platform==joomla is not feedless, config still wins).

Forge CI green on #830 (Tests + Lint). Post-deploy acceptance: verify-811.sh (4 mcp feeds must flip 200->404, 3 joomla feeds stay 200).

Authored-by: Moko Consulting

Promotes #830 to main (triggers deploy-prod). Ships ONLY #811: feedless metadata platforms (npm/mcp/go, feed_format==none) return N/A from their update feed even over a legacy default-joomla update_stream_config row. Genuine Joomla repos unaffected (metadata.platform==joomla is not feedless, config still wins). Forge CI green on #830 (Tests + Lint). Post-deploy acceptance: verify-811.sh (4 mcp feeds must flip 200->404, 3 joomla feeds stay 200). Authored-by: Moko Consulting

jmiller added 3 commits 2026-07-19 06:12:47 +00:00

feat(updateserver): adopt platform registry + feedless metadata platforms return N/A over default-joomla config [#367 #811] ... 5d0d543acc

Rewire the update server's per-platform serve/NotFound gating onto the
platform registry (modules/setting) so the update-feed generator and
wire format for a platform are looked up from config instead of
hardcoded, and fix #811 where npm/mcp/go repos still served a Joomla
updates.xml.

- routers/web/repo/updateserver.go: ServeUpdatesXML and ServeDolibarrJSON
  now gate via services/updateserver.PlatformServesGenerator (registry
  update_generator lookup) plus the "both" compound platform. The other
  Serve* handlers gain a registry-driven IsFeedlessPlatform guard.
- models/updateserver/platform.go: IsFeedlessPlatform is now registry-
  driven (feed_format == "none" covers npm/mcp/go and any admin-configured
  feedless platform), with the static map kept as a fallback.
- #811 precedence fix in ResolvePlatform: a registry-recognized feedless
  metadata platform now overrides the update_stream_config.Platform row,
  including the `NOT NULL DEFAULT 'joomla'` row every licensing-enabled
  repo carries. Genuine Joomla repos (metadata.platform joomla/empty, not
  feedless) still let the config platform win and serve exactly as before;
  an explicit non-joomla config override is still honored for non-feedless
  metadata.

Not built/deployed: no Go toolchain available in this environment; changes
match existing signatures and gofmt style by hand. Requires forge rebuild
+ redeploy.

Authored-by: Moko Consulting <hello@mokoconsulting.tech>

Merge pull request 'chore(sync): cascade main -> dev' (#829) from main into dev c5d34625fd

Merge pull request 'feat(updateserver): adopt platform registry + feedless metadata platforms return N/A over default-joomla config [#367 #811]' (#830) from feature/updateserver-adopt-registry into dev 375fccf12d

jmiller merged commit b39afab766 into main 2026-07-19 06:42:47 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

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

Priority -

Type -

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#831