feat: publish pre-release versions on GitHub without deploying to WP SVN - #993
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. 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. |
There was a problem hiding this comment.
@kasparsd can we just fix this and replace it with 'master' or you'd like to seperate this into a different PR?
There was a problem hiding this comment.
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
left a comment
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
What?
Fixes #822
Why?
How?
Use of AI Tools
Testing Instructions
Screenshots or screencast
Changelog Entry