[uburuntu]

Summary

• update api2ch for the current read-only API, including /api/mobile/v2/boards, /info, /after and /post
• migrate the package to Python 3.14, HTTPX, AnyIO and native Pydantic 2 models
• add explicit raw access, structured errors, caller-owned client injection and atomic streaming downloads
• replace generated legacy models with a verified endpoint matrix, synthetic fixtures and a 1.x migration guide
• build wheel and sdist artifacts in CI and publish those exact artifacts through PyPI Trusted Publishing with OIDC

Upstream verification

The official OpenAPI document is version 1.0.31. Its retrieved SHA-256 is 9d8ced595f2d089e29d61a975677b263f4b0c93307b82c599b9a373382426e55.

Live read-only checks on 16 September 2026 confirmed:

• /boards.json and legacy /makaba/mobile.fcgi reads return 404
• board, catalog, page and full-thread JSON routes remain available
• catalog, page and thread responses now contain a nested board object
• page responses may use files: null
• missing mobile resources use HTTP 200 error envelopes

The integration suite discovers a current non-adult thread at runtime instead of depending on a historical thread.

Verification

• ruff format --check api2ch tests examples
• ruff check api2ch tests examples
• mypy api2ch
• 12 deterministic offline tests passed
• 2 live integration tests passed, sync and async
• wheel and sdist built and passed strict metadata checks
• both distributions installed and imported as version 2.0.0 outside the source tree

Release setup

Before the first release, create a protected pypi environment and configure the PyPI Trusted Publisher documented in RELEASING.md.