Call + (44) 0843 289 4539

  • No products in the cart.

Updating wordpress plugin subversion

Our WordPress plugin Stop Web Crawlers is available for download from plugin.  We are currently learning and refining everything our approach to listing our products on this amazing directory.

We’re having to integrate a number of our own internal tools and processes to adapt to include the tools.  We have previously posted about integrating Git, GitHub and subversion into the plug-in software development lifecycle.

We have also had to become familiar with the finer workings of subversion, due our version control system of choice internally is Git. However, we need to understand how to create branches and tags in subversion in order to create updates for plug-ins.

This post just discusses the steps required to update a plug-in using the terminal based subversion client.  You will need to ensure you have installed subversion on your mac using the homebrew package manager


Clone your subversion repository

svn co

Now change into the trunk directory

cd stop-web-crawlers/trunk

Our main development branch will always be within GitHub, and developers will largely follow the process as defined Git, GitHub and Subversion workflow. However, once it comes to managing the releases we still at this stage prefer to do the tagging and updating within subversion.

So the first part of the process of creating a release is to first update the readme.txt with the updated version number.

=== Stop Web Crawlers ===
Contributors: Gary Woodfine
Donate link:
License: GPLv3
License URI:
Tags: block bot, block bots, block bad bots, stop bot, stop bots, stop bad bots, stop web crawlers, web crawlers
Tested up to: 4.5
Stable tag: 1.0.4    <-- We update the version here

And then we update the version number in main plugin PHP file i.e. stop-web-crawlers.php

 Plugin Name: Stop Web Crawlers
 Plugin URI:
 Description: Blocks traffic referrer spam bots
 Version: 1.0.4   <-- Update the version number here
 Author: Three Nine Consulting
 Author URI:
 License: GPLv2 or later

Once we are confident that the plugins passes all tests and Quality is assured, we create a new tag version and copy the contents of trunk into the tag.

svn cp trunk tags/1.0.4

We then commit this new version to subversion

svn ci -m "tagging version 1.0.4"

We then wait approximately 15 minutes and the new version will be available for download from the directory and all exisiting users will be notified that they need to update the plugin.

Follow Me

Gary Woodfine

Helps businesses by improving their technical proficiencies and eliminating waste from the software development pipelines.

A unique background as business owner, marketing, software development and business development ensures that he can offer the optimum business consultancy services across a wide spectrum of business challenges.
Follow Me