Title: Plugin updated to new version after commit on trunk
Last modified: August 30, 2016

---

# Plugin updated to new version after commit on trunk

 *  Resolved [Joao Romao](https://wordpress.org/support/users/joaoromao/)
 * (@joaoromao)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/plugin-updated-to-new-version-after-commit-on-trunk/)
 * Hey guys, quick question. We’ve been developing a plugin over the last year and
   has been great so far, development-wise.
 * However, last evening we (as usual) committed our development changes into our
   trunk folder. What changed was this was actually interpreted as a new plugin 
   version and thus all new users (and those who updated) got the trunk version 
   of our plugin.
 * To worsen things up, this version was not linking to our servers, rather it was
   connected to 127.0.0.1 so in just a few hours we got about 2,000 users unable
   to use our tool.
 * Anyone has an idea of what might have happened here and how we can avoid it in
   the future?
 * Thanks in advance,
    John.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [Konstantin Obenland](https://wordpress.org/support/users/obenland/)
 * (@obenland)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/plugin-updated-to-new-version-after-commit-on-trunk/#post-6839466)
 * Hi Joao,
 * What happened was that the stable tag in trunk’s `readme.txt` was updated to 
   3.0 ([[1305606]](https://plugins.trac.wordpress.org/changeset/1305606/wp-share-buttons-analytics-by-getsocial#file9))
   but the plugin didn’t receive a 3.0 tag. With the tag missing, the directory 
   has nowhere to point to but trunk, as the canonical source of truth.
 * To avoid that from happening in the future, I’d recommend tagging a new release
   before you commit to trunk, and then commit both the trunk changes and the new
   tag.
 * Konstantin
 *  Thread Starter [Joao Romao](https://wordpress.org/support/users/joaoromao/)
 * (@joaoromao)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/plugin-updated-to-new-version-after-commit-on-trunk/#post-6839467)
 * Konstantin, that makes sense. I’m passing this info to the development team.
 * Thanks for the answer.
    John.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin updated to new version after commit on trunk’ is closed to new
replies.

## Tags

 * [development](https://wordpress.org/support/topic-tag/development/)
 * [trunk](https://wordpress.org/support/topic-tag/trunk/)

 * In: [Everything else WordPress](https://wordpress.org/support/forum/miscellaneous/)
 * 2 replies
 * 2 participants
 * Last reply from: [Joao Romao](https://wordpress.org/support/users/joaoromao/)
 * Last activity: [10 years, 5 months ago](https://wordpress.org/support/topic/plugin-updated-to-new-version-after-commit-on-trunk/#post-6839467)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics