search

spatie / wordpress-ray

Debug with Ray to fix problems faster in WordPress apps
https://myray.app
MIT License
73 stars 14 forks source link

WordPress.org and plugin releases #19

Closed slaFFik closed 3 years ago

slaFFik commented 3 years ago

I see that you made a release 1.0.1: image

But WordPress.org is not aware of it and still allows everyone to download 1.0.0 by default: image

That's because in your trunk/readme.txt you still point to the 1.0 which automatically instructs WP.org to zip and distribute the tags/1.0.0.

To make the 1.0.1 release go live and instruct WP.org to use tags/1.0.1 as the source of the zip you need to update in trunk/readme.txt the Stable tag: 1.0 to Stable tag: 1.0.1. Just creating a new directory inside SVN tags/ is not enough And you will need to do this step for each and every release.

Basically, your trunk/* can always be the same as the latest tag you want to release. And for each release, you need to manually increment the Stable tag: X.X.X value inside the readme.txt. You can leave in trunk/ only one readme.txt file and remove all the rest (and still update it and increment the Stable tag for each release), but I find it easier to just copy the release-prepared code to both tags/X.X.X and trunk/.

Here is the interface I used to identify this issue: https://plugins.trac.wordpress.org/browser/spatie-ray/

freekmurze commented 3 years ago

Thanks, I hope I've done everything right in 1.0.2 🙂