Plan: Forgejo PyPI Migration — CI Pipelines for All Python Repos

Vision

Projects & Repos Touched

Context

• [x] Forgejo PyPI registry verified and operational
• [x] ~/.pypirc configured for Forgejo
• [x] Woodpecker global secrets set: forgejo_publish_user, forgejo_publish_token, forgejo_pypi_url, forgejo_url, forgejo_user, forgejo_password
• [x] woodpecker-sdk pipeline template proven (PR #6, plan-2026-02-28-woodpecker-sdk-mcp Phase 2)
• [x] All Phase 1 + Phase 2 repos activated in Woodpecker (16 of 16 non-remote repos)
• [x] Phase 1 complete: 4/4 repos merged, pipelines green, packages published to Forgejo PyPI
• [x] Phase 2 complete: 9/9 repos merged, all pipelines green, packages published to Forgejo PyPI (2026-03-01)
• [x] All 13 packages verified installable from Forgejo PyPI via pip install --index-url (2026-03-01)

Previous Plan

Depends On

Decisions Made

Phases

Phase 1 — Forgejo-native repos (COMPLETE)

• Repos activated BEFORE merge miss the push webhook — use Forgejo API commit to trigger
• Old .woodpecker.yaml files cause dual-config loading — MUST delete before adding .woodpecker.yml
• Stale repo-level pypi_token secrets cause pipeline errors when deleted but still referenced
• forgejo-sdk tests require forgejo_url/forgejo_user/forgejo_password secrets — added as globals
• Poetry-core build backend doesn't expose dev deps as pip extras — test step needs explicit pip install
• 409 Conflict on publish = version already exists in registry (expected, bump version to fix)
• Woodpecker repos can be activated via API: POST /api/repos?forge_remote_id={id} (no UI needed)
• Woodpecker secret hierarchy: global > org > repo (most specific wins). Global secrets are ideal for shared Forgejo PyPI creds.

Phase 2a — Pre-work (COMPLETE)

• [x] Deleted stale pypi_token repo-level secrets from all 9 repos (Woodpecker IDs 7-15). Non-pypi secrets (notion_api_key, google_oauth_token, linkedin_*) left in place for test steps.
• [x] Checked for old .woodpecker.yaml files — confirmed present in all 9 repos (deleted by agents as part of pipeline swap)
• [x] Switched local git origin from GitHub to Forgejo for 6 cloned repos: gcal-sdk, linkedin-sdk, notion-mcp, gmail-mcp, linkedin-mcp-scheduler, mcp-remote-auth
• [x] Cloned 3 missing repos from Forgejo: gmail-sdk, notion-sdk, gcal-mcp
• [x] Pulled latest from Forgejo on all 9 repos — all local clones now current with Forgejo main

Phase 2b — Pipeline swap (COMPLETE)

Phase 3 — Remote MCP proxies (low priority, may deprecate)

Phase 4 — Yank public pypi.org packages + update references

Key Files

Verification

• [x] All Phase 1 repos (4/4) have .woodpecker.yml + ruff config + published to Forgejo PyPI
• [x] Woodpecker pipelines green on all Phase 1 repos
• [x] pal-e-docs-mcp PR reviewed, merged, pipeline verified
• [x] Phase 2a pre-work complete: secrets cleaned, origins switched, repos cloned
• [x] Phase 2b: 9/9 PRs opened, QA-reviewed, merged
• [x] Phase 2b: All 9 Woodpecker pipelines green, packages published to Forgejo PyPI
• [x] pip install --index-url {forgejo} {package} verified for all 13 packages (2026-03-01)
• [ ] Public pypi.org packages yanked (Phase 4)

Next Plan Seeds

• Automated version bumping (tag-based release across all repos)
• Shared .woodpecker.yml template repo (DRY pipeline config)
• Local pip config to default to Forgejo index (pip config set global.index-url)

Related

• plan-2026-02-28-woodpecker-sdk-mcp — Phase 2 established the pattern (reference implementation)
• todo-forgejo-pypi — originating TODO
• todo-ruff-standardization — ruff config standardization (achieved by this plan)
• plan-2026-02-25-mcp-gateway-migration — may deprecate Phase 3 repos
• service-onboarding-sop — container images → Harbor, Python packages → Forgejo