Simplify updater to @mosaic/mosaic only and fix Gitea wrapper repo context #387

Closed
opened 2026-04-05 01:57:38 +00:00 by jason.woltje · 0 comments
Owner

Problem

  • The updater fix merged in #384 still carries legacy @mosaic/cli compatibility that is no longer needed. Jason approved a breaking change; only @mosaic/mosaic matters.
  • The Gitea wrapper flow is brittle in this environment because tea requires explicit repo/login context. This caused wrapper-driven merge attempts to fail even though CI and PR state were fine.

Acceptance criteria

  • Remove legacy updater fallback logic and tests; updater targets @mosaic/mosaic only.
  • Keep/update version bumps as needed for a releaseable fix.
  • Fix the repo-source wrappers so PR merge/CI/issue-close operations work reliably on Gitea from a normal repo checkout.
  • Add or update tests for the wrapper logic if practical; otherwise provide direct verification evidence.
  • Push branch, open PR, pass CI, merge squash, and close issue.
Problem - The updater fix merged in #384 still carries legacy @mosaic/cli compatibility that is no longer needed. Jason approved a breaking change; only @mosaic/mosaic matters. - The Gitea wrapper flow is brittle in this environment because tea requires explicit repo/login context. This caused wrapper-driven merge attempts to fail even though CI and PR state were fine. Acceptance criteria - Remove legacy updater fallback logic and tests; updater targets @mosaic/mosaic only. - Keep/update version bumps as needed for a releaseable fix. - Fix the repo-source wrappers so PR merge/CI/issue-close operations work reliably on Gitea from a normal repo checkout. - Add or update tests for the wrapper logic if practical; otherwise provide direct verification evidence. - Push branch, open PR, pass CI, merge squash, and close issue.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#387