pal-e-docs

Phase 8f-1: SDK Publish Pipeline

phase-postgres-8f1-sdk-publish Phase

Project
Goal: Get pal-e-docs-sdk published to Forgejo PyPI so the MCP server can depend on it as a registry package.
Owner: Dev agent
Repo: forgejo_admin/pal-e-docs-sdk
Depends on: 8e (SDK code complete and tested)

Scope

The SDK repo has a .woodpecker.yaml with lint + test + publish steps, but the repo was never activated in Woodpecker. The publish pipeline has never run. The package is not on Forgejo PyPI (14 packages listed, pal-e-docs-sdk not among them). This sub-phase activates the pipeline and verifies end-to-end publish.
Blocks: 8f-2 — MCP server's pyproject.toml can't resolve pal-e-docs-sdk>=0.1.0 without this.

Progress

  • Woodpecker activated — repo ID 26, responding to push/pull_request events
  • Secrets configured — paldocs_base_url repo secret created; global PyPI secrets already available
  • PR #15 merged — ruff formatting fix. QA approved. Squash merged to main.
  • Forgejo issue #14 — created by dev agent for the formatting fix
  • Pipeline #4 running — push-to-main with publish step. Awaiting completion.

Remaining

  • Verify pipeline #4 passes (lint + test + publish)
  • Verify pal-e-docs-sdk v0.1.0 appears on Forgejo PyPI
  • Verify pip install from Forgejo PyPI works

Deliverables

  • Woodpecker repo activation (ID 26)
  • Repo secret: paldocs_base_url
  • PR #15 — ruff formatting fix (merged)
  • Forgejo issue #13 (original), #14 (formatting fix by dev agent)
  • phase-postgres-8f-mcp-rewrite — parent sub-phase
  • todo-forgejo-pypi — Forgejo PyPI pattern (status: done)
  • phase-postgres-8f2-mcp-rewrite-core — blocked by this