please tag releases

I’ll start tagging my plugins as it’s technically the recommended method WP suggests. But I can’t really see a reason for needing access to old versions. Can you explain why you need access for old versions of the plugin?

Rollback in case of emergency, or installing from source with Composer via something like WPackagist.

@eclev91 – You’re 100% right, thank you for bringing this to my attention. I will start updating my plugins correctly from now on ??

Following up on this @wpexplorer – it looks like you’re only tagging the latest release. This breaks any install operations from source locked to an older version.

Ideally old releases would continue to be in the tags directory. It’s possible that this is just a side-effect of starting to tag releases though. I can’t see the dates of the latest releases and can’t say for sure.

@eclev91 – You are correct, this is a result of starting to tag releases because the old ones won’t be there. I guess I could go back and try and locate old versions of the plugin in my iMac time capsule and upload them to the SVN directory.

But I’m wondering what’s actually causing things to break. I’m not sure what you mean by “This breaks any install operations from source locked to an older version”.

Are you saying you have installs setup to only load a specific version of the plugin?

By the way, I actually have a 1.5 update that I was planning to release this week with various new options and changes to the default HTML to use modern flex styles. If you are interested to try it out before the official release you can download it out here.

ps: If you personally have access to some of the old versions you are referring to feel free to email me directly at wpexplorer [at] gmail dot com and I’ll upload those to the tag releases dir.

I wouldn’t get hung up on populating old ones at this point unless someone specifically needed them.

Our WP sites are managed with Composer, so plugins are all required at specific versions via a lockfile. If the source disappears, then future composer install runs fail because the code is no longer out there. We run updates about monthly, but in between those updates ,if we want to spin up a copy of the site without updating dependencies and this plugin has updated since then, it can’t install this plugin.

See https://wpackagist.org/