Complete stage-2 migration cleanup for zaojun #37

Closed
opened 2026-08-18 06:44:52 +00:00 by agent-pi · 2 comments
Collaborator

The repo's origin remote already points to forge.marvin8.zone (stage 1 complete), but the remaining stage-2 cleanup from the migration plan is still outstanding.

Remaining work:

  • A handful of Codeberg references remain in docs, ROADMAP-detail.md, and mkdocs.yml that still point at the old host or name Codeberg.
  • Dependencies have not yet been re-checked against PyPI for updates.
  • The security posture has not been re-verified.
  • The migration tracker has not yet been marked stage 1 + 2 complete.
The repo's `origin` remote already points to forge.marvin8.zone (stage 1 complete), but the remaining stage-2 cleanup from the migration plan is still outstanding. Remaining work: - A handful of Codeberg references remain in docs, ROADMAP-detail.md, and mkdocs.yml that still point at the old host or name Codeberg. - Dependencies have not yet been re-checked against PyPI for updates. - The security posture has not been re-verified. - The migration tracker has not yet been marked stage 1 + 2 complete.
Author
Collaborator

Exploration findings:

  • No claude / codeberg-agent remotes remain — already removed.
  • CI runner is already zhuiri (local); no codeberg-small-lazy references.
  • No Containerfile — container publishing is N/A.
  • Docs already publish to zaojun.marvin8.zone via grebedoc; the codeberg.org/git-pages/action@v2 upload step stays as-is.
  • pyproject.toml project 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:

  1. Update the remaining Codeberg references listed above.
  2. Run zaojun and bump non-up_to_date deps to the ~= minimum.
  3. Run pysentry and address every vulnerability.
  4. Run the full check suite (ruff, ty, complexipy, pytest).
  5. Update the migration tracker, commit, push to forge-pi, open PR.

Branch: feat/issue-37-complete-stage2-migration

Exploration findings: - No `claude` / `codeberg-agent` remotes remain — already removed. - CI runner is already `zhuiri` (local); no `codeberg-small-lazy` references. - No Containerfile — container publishing is N/A. - Docs already publish to zaojun.marvin8.zone via grebedoc; the `codeberg.org/git-pages/action@v2` upload step stays as-is. - `pyproject.toml` project 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: 1. Update the remaining Codeberg references listed above. 2. Run zaojun and bump non-up_to_date deps to the `~=` minimum. 3. Run pysentry and address every vulnerability. 4. Run the full check suite (ruff, ty, complexipy, pytest). 5. Update the migration tracker, commit, push to forge-pi, open PR. Branch: `feat/issue-37-complete-stage2-migration`
Author
Collaborator

Status 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/action upload URL, CHANGELOG.md history, and redirect.js remain), and the stale ROADMAP.md/ROADMAP-detail.md tracker files were deliberately removed in 952d57b rather 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:

  1. Fresh dependency re-check — run zaojun --format json (project config: cache, groups, min-age) and bump every non-up_to_date package to its ~= minimum (aged_version for too_new, latest otherwise), align pre-commit hook revs, regenerate pylock.toml, update uv.lock.
  2. Fresh security posture verificationuv run nox -s pysentry locally; 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.

Status 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/action` upload URL, `CHANGELOG.md` history, and `redirect.js` remain), and the stale `ROADMAP.md`/`ROADMAP-detail.md` tracker files were deliberately removed in 952d57b rather 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: 1. **Fresh dependency re-check** — run `zaojun --format json` (project config: cache, groups, min-age) and bump every non-`up_to_date` package to its `~=` minimum (`aged_version` for `too_new`, `latest` otherwise), align pre-commit hook revs, regenerate `pylock.toml`, update `uv.lock`. 2. **Fresh security posture verification** — `uv run nox -s pysentry` locally; 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.
agent-pi referenced this issue from a commit 2026-09-13 20:45:19 +00:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/zaojun#37
No description provided.