Automate Gitea and GitHub releases from Changesets on tag push #60

Closed
opened 2026-09-01 16:00:38 +00:00 by eleith · 1 comment
Owner

Goal

Automatically publish release notes on Gitea and GitHub Releases when release tags (@when/web@*, etc.) are pushed to the repository.

Background

Currently, running pnpm version:apps consumes Changesets and updates package-level changelogs (apps/web/CHANGELOG.md, apps/cli/CHANGELOG.md, apps/worker/CHANGELOG.md), but does not publish aggregated repository-level releases on Gitea or GitHub.

Proposed Solution

Add a release publishing step to CI workflows:

  1. GitHub Actions: In .github/workflows/web.yml (or a dedicated workflow), parse the latest version notes from apps/web/CHANGELOG.md and call softprops/action-gh-release@v2 (or gh release create) on tag push.
  2. Woodpecker CI / Gitea: In .woodpecker/web.yml, use plugins/gitea-release to publish the release to Gitea with the extracted changelog notes.
### Goal Automatically publish release notes on Gitea and GitHub Releases when release tags (`@when/web@*`, etc.) are pushed to the repository. ### Background Currently, running `pnpm version:apps` consumes Changesets and updates package-level changelogs (`apps/web/CHANGELOG.md`, `apps/cli/CHANGELOG.md`, `apps/worker/CHANGELOG.md`), but does not publish aggregated repository-level releases on Gitea or GitHub. ### Proposed Solution Add a release publishing step to CI workflows: 1. **GitHub Actions**: In `.github/workflows/web.yml` (or a dedicated workflow), parse the latest version notes from `apps/web/CHANGELOG.md` and call `softprops/action-gh-release@v2` (or `gh release create`) on tag push. 2. **Woodpecker CI / Gitea**: In `.woodpecker/web.yml`, use `plugins/gitea-release` to publish the release to Gitea with the extracted changelog notes.
eleith added the enhancement label 2026-09-01 18:49:33 +00:00

Closing for now at the owner’s request. Automated repository Release publishing and formatting are not needed yet; this can be reopened when we want more formal release presentation. Existing Changesets versioning, tags and container publishing remain unchanged.

Closing for now at the owner’s request. Automated repository Release publishing and formatting are not needed yet; this can be reopened when we want more formal release presentation. Existing Changesets versioning, tags and container publishing remain unchanged.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eleith/when#60