Complete stage-2 migration cleanup for zaojun #37
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
marvin8/zaojun#37
Loading…
Reference in a new issue
No description provided.
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?
The repo's
originremote already points to forge.marvin8.zone (stage 1 complete), but the remaining stage-2 cleanup from the migration plan is still outstanding.Remaining work:
Exploration findings:
claude/codeberg-agentremotes remain — already removed.zhuiri(local); nocodeberg-small-lazyreferences.codeberg.org/git-pages/action@v2upload step stays as-is.pyproject.tomlproject URLs are already forge.marvin8.zone.Remaining tracked Codeberg references to fix: mkdocs.yml (taibai LICENSE link — taibai is migrated to marvin8/taibai), ROADMAP-detail.md (2), docs/development/contributing.md (1), docs/reference/changelog.md (2). Left alone: CHANGELOG.md (off-limits) and docs/javascripts/redirect.js (intentional redirect from the old domain).
Plan:
~=minimum.Branch:
feat/issue-37-complete-stage2-migrationStatus refresh (2026-09-13): most of this was already landed by PR #38 (merged 2026-08-18) — Codeberg references are clean (only the intentional
git-pages/actionupload URL,CHANGELOG.mdhistory, andredirect.jsremain), and the staleROADMAP.md/ROADMAP-detail.mdtracker files were deliberately removed in952d57brather than ticked. Stage 1 = PR #36 (merged), stage 2 = PR #38 (merged); closing this issue with evidence completes the tracker step.What is genuinely outstanding after ~4 weeks:
zaojun --format json(project config: cache, groups, min-age) and bump every non-up_to_datepackage to its~=minimum (aged_versionfortoo_new,latestotherwise), align pre-commit hook revs, regeneratepylock.toml, updateuv.lock.uv run nox -s pysentrylocally; gitleaks runs on the PR itself in CI.This lands together with #39 (range-advisory scanning) and the Release-Notes reset recipe split in one branch/PR.