For the purpose of this exercise, I’m going to update the Tested up to value for my Stop Emails plugin, without creating a new release.
Get Your Subversion Repository URL
This URL is available on the Developers tab of your plugin on wordpress.org in the Subversion Repository link. In my case, the url is http://plugins.svn.wordpress.org/stop-emails/.
Checkout a Local Copy of the Subversion Repo
svn co http://plugins.svn.wordpress.org/stop-emails/
Navigate into your plugin directory with something like
Update Your “Tested up to” Value
You should updated your “Tested up to” value in your latest tagged release. Look in
tags/ and find the latest version, in my case
1.2.1. If you want to edit this from the command line, you can use
You can review the change by using
Push the changes back to wordpress.org
You then check-in your changes and include a message of the change.
svn ci -m "Tested up to bumped to 5.9 in tagged release 1.2.1"
My Block X-ray Attributes Plugin
In order to make my life easier, I’ve made these notes for updating my Block X-ray Attributes plugin.
svn co http://plugins.svn.wordpress.org/block-xray-attributes/
svn ci -m "Tested up to bumped to 6.3 in tagged release 1.2.0"
My Modify Comment Parent Plugin (Trunk Based)
In order to make my life easier, I’ve made these notes for updating my Modify Comment Parent plugin.
Note: While in my other two plugins I have my code in the
tags folders, where the code for all my previous versions is available in the SVN repository.
This plugin is different in that I only have code in the
trunk folder. I only have the the latest code in the SVN repository (though the development history is all available at https://github.com/salcode/modify-comment-parent).
The only impact of using
trunk instead of a folder in
tags is the path to
readme.txt is slightly different.
svn co http://plugins.svn.wordpress.org/modify-comment-parent/
svn ci -m "Tested up to bumped to 6.3 in trunk"
Why I Wrote this Post
The only time I ever use subversion is for managing my plugin on wordpress.org. Every time I use it, I have to look up how.
For tagged releases (e.g. version 1.2.1) I use a deploy script written by others smarter than I and more well versed in subversion. Creating a tagged release for a bump in the Tested up to value would be overkill.