Skip to content

Chain WordPress.org deploy into publish-release.yml #843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andypotanin merged 1 commit into from
Sep 2, 2026
Merged

Chain WordPress.org deploy into publish-release.yml #843

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .github/workflows/publish-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@
prerelease:
description: 'Pre-release version (e.g. RC1, beta, etc...)'
required: false
deploy_wporg:
description: 'Deploy to WordPress.org after release (skipped for pre-releases)'
required: false
default: true
type: boolean

permissions:
contents: write
Expand All @@ -24,3 +29,13 @@
tag: ${{ github.event.inputs.tag }}
version: ${{ github.event.inputs.version }}
prerelease: ${{ github.event.inputs.prerelease }}

deploy-wporg:
if: ${{ inputs.deploy_wporg && !inputs.prerelease }}
needs: release
uses: udx/reusable-workflows/.github/workflows/wp-org-svn-deploy.yml@master
with:
tag: ${{ github.event.inputs.tag }}

@devin-ai-integration devin-ai-integration Bot Sep 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Distinct release tags misname packages

When tag differs from the plugin version, deploy-wporg names the WordPress.org package after the GitHub tag. The stable version then has no matching SVN package.

Prompt for agents 
The publish workflow supports separate tag and version inputs, but wp-org-svn-deploy.yml accepts only tag and passes it to the 10up deploy action as VERSION. Extend the reusable workflow to accept the WordPress plugin version separately from the Git checkout tag, then pass the caller's version input to it. Preserve the existing release workflow's fallback behavior when version is omitted, such as deriving the stable version from readme.txt, so tags like 1.2.3a or v1.2.3 can still deploy the correct WordPress.org tags/<version> directory.
Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

secrets:
svn_username: ${{ secrets.SVN_USERNAME }}
svn_password: ${{ secrets.SVN_PASSWORD }}
Loading