Skip to content

ci(wordpress): record plugin releases as GitHub releases - #55

Merged
bendersej merged 1 commit into
mainfrom
wordpress-github-release
Sep 28, 2026
Merged

bendersej merged 1 commit into
mainfrom
wordpress-github-release

Conversation

@bendersej

Copy link
Copy Markdown
Member

Background

WordPress plugin releases go through WordPress.org SVN, so GitHub has no record of them. The WordPress release workflow now leaves one: a wordpress@<version> GitHub release, which also marks the version as announced.

Changes

  • The WordPress release workflow creates a wordpress@<version> GitHub release on the commit it runs from, with the README.txt changelog entries
  • The release is never marked Latest, so the badge stays on the SDK packages
  • A version whose GitHub release already exists is skipped, so running the workflow twice never posts twice on Discord
  • Order: live on WordPress.org, not yet released, Discord post, GitHub release; a failed Discord post leaves no release, so a rerun is safe
  • The release steps in wordpress/README.md describe it

@bendersej
bendersej merged commit cf43150 into main Sep 28, 2026
6 checks passed
@bendersej
bendersej deleted the wordpress-github-release branch September 28, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant