feat: post release notes to Fediverse via taibai #75

New issue

Closed

opened 2026-05-24 07:54:18 +00:00 by coding-agent-marvin8 · 1 comment

coding-agent-marvin8 commented

2026-05-24 07:54:18 +00:00

(Migrated from codeberg.org)

Add a workflow that posts structured release notes to a Fediverse account whenever a new release is published, modelled on the longwei project.

Changes:

Create Release-Notes.md (taibai thread format)
Create .woodpecker/fediverse.yml (post on release only)
Add validate step to .woodpecker/checks.yml (dry-run on every PR/tag/release)
Add tool.bumpversion.files entry for Release-Notes.md in pyproject.toml
Add release-notes maintenance rules to CLAUDE.md

Secrets needed in Woodpecker CI:

TAIBAI_INSTANCE_URL
TAIBAI_ACCESS_TOKEN

Add a workflow that posts structured release notes to a Fediverse account whenever a new release is published, modelled on the longwei project. Changes: - Create Release-Notes.md (taibai thread format) - Create .woodpecker/fediverse.yml (post on release only) - Add validate step to .woodpecker/checks.yml (dry-run on every PR/tag/release) - Add [[tool.bumpversion.files]] entry for Release-Notes.md in pyproject.toml - Add release-notes maintenance rules to CLAUDE.md Secrets needed in Woodpecker CI: - TAIBAI_INSTANCE_URL - TAIBAI_ACCESS_TOKEN

coding-agent-marvin8 commented

2026-05-24 07:54:43 +00:00

(Migrated from codeberg.org)

Exploration findings:

longwei uses uvx taibai thread Release-Notes.md — no install step needed, uvx fetches it ephemerally.
Validation (dry-run) moves into checks.yml so it runs on every PR/tag/release alongside the existing test suite.
fediverse.yml is posting-only, gated to release events, depends_on: [checks].
bump-my-version needs a tool.bumpversion.files entry matching "feed2fedi {current_version}" in the intro post header.
CLAUDE.md already has an uncommitted ## Git block that will be folded into this PR.

Plan:

Add validate_release_notes step to .woodpecker/checks.yml
Create .woodpecker/fediverse.yml (post only)
Add tool.bumpversion.files to pyproject.toml
Create Release-Notes.md (template at 3.7.5)
Update CLAUDE.md (fold in ## Git block + add release-notes rules)

Exploration findings: - longwei uses `uvx taibai thread Release-Notes.md` — no install step needed, uvx fetches it ephemerally. - Validation (dry-run) moves into checks.yml so it runs on every PR/tag/release alongside the existing test suite. - fediverse.yml is posting-only, gated to release events, depends_on: [checks]. - bump-my-version needs a [[tool.bumpversion.files]] entry matching "feed2fedi {current_version}" in the intro post header. - CLAUDE.md already has an uncommitted `## Git` block that will be folded into this PR. Plan: 1. Add validate_release_notes step to .woodpecker/checks.yml 2. Create .woodpecker/fediverse.yml (post only) 3. Add [[tool.bumpversion.files]] to pyproject.toml 4. Create Release-Notes.md (template at 3.7.5) 5. Update CLAUDE.md (fold in ## Git block + add release-notes rules)