I’m the author of the “AutoChimp” plugin. I recently checked in a bunch of code for my 2.0 version. It is NOT tagged (my trunk/readme.txt file is still on my old version and I don’t have a 2.0 folder in my tag folder)…yet the 2.0 version is prematurely public. I can’t understand why. This has never happened before.
Hey did you ever get to the bottom of this? I just had the exact same thing.
I have 1.0.1 as the stable version which is tagged and has been live for a few days. 1.1 is in trunk being worked on, no tag as of yet. But WordPress just pushed 1.1 out as the current stable version! The stable tag is definitely still 1.0.1 in trunk/readme.txt so why is 1.1 being made available? And how is that even possible when I’ve not created a 1.1 tag yet?!
Ah… I believe I just found the issue, I hadn’t checked in the 1.0.1 stable tag, I’d made the copy but somehow forgot to check it in. As such WordPress.org had been serving up the version in trunk because it couldn’t find the 1.0.1 tag. Oops!
I’ve created the 1.0.1 tag and the 1.1 tag and moved to 1.1 as stable, here’s hoping that’s the last of the issue and I can now safely check in to trunk without making those files live.
Viewing 3 replies - 1 through 3 (of 3 total)
The topic ‘Tagging problem??’ is closed to new replies.