Add CHANGELOG and publish it as release notes; auto-open next-version bump PR #97

Merged

thatguygriff merged 1 commits from feature/changelog-release-notes into main 2026-07-23 19:54:40 +00:00

Conversation 0 Commits 1 Files Changed 2

+118 -2

thatguygriff commented 2026-07-23 19:35:55 +00:00

Owner

Copy Link

Copy Source

What

• Add CHANGELOG.md — one section per version, newest first. The top section always reflects the current plugin header version; release status is purely a matter of whether a tag exists (no Unreleased section, no dates).
• Release workflow now extracts the tagged version's changelog section and publishes it as the Gitea release body (POST on create; PATCH when the release was pre-created via the UI).
• New bump-version job runs after a stable release: bumps the plugin to the next patch version (header + USC_VERSION), inserts a fresh empty changelog section, and opens a PR. Skipped for pre-release tags (those containing a hyphen).

Tests

No PHP changed (only CHANGELOG.md and .gitea/workflows/release.yml), so composer test/lint/cs were not run locally; CI lint/static-analysis/test still run on this PR.

Follow-up

First release after merge will exercise the release-notes extraction and the auto-bump PR — worth confirming the GITHUB_TOKEN has branch-push + pulls rights on that run.

## What - Add `CHANGELOG.md` — one section per version, newest first. The top section always reflects the current plugin header version; release status is purely a matter of whether a tag exists (no `Unreleased` section, no dates). - Release workflow now extracts the tagged version's changelog section and publishes it as the Gitea release body (POST on create; PATCH when the release was pre-created via the UI). - New `bump-version` job runs after a stable release: bumps the plugin to the next patch version (header + `USC_VERSION`), inserts a fresh empty changelog section, and opens a PR. Skipped for pre-release tags (those containing a hyphen). ## Tests No PHP changed (only `CHANGELOG.md` and `.gitea/workflows/release.yml`), so `composer test`/`lint`/`cs` were not run locally; CI lint/static-analysis/test still run on this PR. ## Follow-up First release after merge will exercise the release-notes extraction and the auto-bump PR — worth confirming the `GITHUB_TOKEN` has branch-push + pulls rights on that run.

thatguygriff added 1 commit 2026-07-23 19:35:55 +00:00

Add CHANGELOG and publish it as release notes; auto-open next-version bump PR ... 4bca2fbc96

Add CHANGELOG.md (one section per version, newest first; the top section
always reflects the current plugin header version — release status is
purely a matter of tagging).

The Release workflow now extracts the tagged version's changelog section
and publishes it as the Gitea release body (POST on create, PATCH when the
release was pre-created via the UI). After a stable release, a new
bump-version job bumps the plugin to the next patch version, opens a fresh
changelog section, and opens a PR. Pre-release tags are skipped.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

thatguygriff merged commit bba24566a6 into main 2026-07-23 19:54:40 +00:00

thatguygriff deleted branch feature/changelog-release-notes 2026-07-23 19:54:41 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

enhancement

Extends an existing feature

feature

New user-facing capability

payments

Billing, Stripe, receipts, reporting

security

Security vulnerability or hardening

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

thatguygriff (James Griffin-Allwood)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Unsupervised/unsupervised-scheduler#97