Skip to content

feat: publish pre-release versions on GitHub without deploying to WP SVN - #993

Merged
kasparsd merged 3 commits into
masterfrom
add-prelease-builds
Sep 25, 2026
Merged

kasparsd merged 3 commits into
masterfrom
add-prelease-builds

Conversation

@kasparsd

@kasparsd kasparsd commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

What?

Fixes #822

Why?

  • Don't deploy pre-release GitHub releases to WP SVN.

How?

Use of AI Tools

Testing Instructions

Screenshots or screencast

Before After

Changelog Entry

Development Update - Support for publishing pre-release versions of plugin to GitHub for testing.

Open WordPress Playground Preview

@github-actions

github-actions Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: kasparsd <kasparsd@git.wordpress.org>
Co-authored-by: masteradhoc <masteradhoc@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


- name: WordPress.org asset and readme update
uses: 10up/action-wordpress-plugin-asset-update@2480306f6f693672726d08b5917ea114cb2825f7 # v2.2.0
# FIXME: The trunk branch doesn't exist so this does nothing on merges to the master branch.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@kasparsd can we just fix this and replace it with 'master' or you'd like to seperate this into a different PR?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

if we enable this on master then whatever is merged to master gets deployed to SVN trunk, marking it the "stable" release version. Secondly, the release workflow currently merges to master first and then creates a tag so the stable release would be marked before the tag release is actually deployed.

All that to say -- I believe we don't want to enable it now.

@masteradhoc masteradhoc left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks great, thank you for the work on this! If you feel we can do the "FIXME" comment as part of this PR fine for me - else we can do it on a seperate one.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The remaining documentation nit is minor and does not block approval.

Review effort: Lite
Findings: None

What changed in this PR

Updates release automation to publish pre-release plugin ZIPs on GitHub without deploying them to WordPress.org.

Changes:

  • Documents beta and release-candidate procedures.
  • Uses dry-run deployment for pre-releases.
  • Uploads generated ZIPs as GitHub release assets.
File Description
RELEASING.md Adds pre-release publishing guidance.
.github/​workflows/​deploy.yml Skips WordPress.org deployment while generating and uploading ZIPs.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@kasparsd
kasparsd merged commit 72effa5 into master Sep 25, 2026
29 of 31 checks passed
@kasparsd
kasparsd deleted the add-prelease-builds branch September 25, 2026 14:59
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.

Document process for pre-releases

3 participants