Keep older versions on new releases

[joe4dev]

Could you keep older versions when you release a new version on https://wordpress.org/plugins/fakerpress/ ?
Automatic plugin installation via wp-cli (http://wp-cli.org/) will fail otherwise (e.g., wp plugin install fakerpress --version=0.2.2 attempts to install version 0.2.2 which is not available anymore)

[bordoni]

Yes, that is a problem that I need to fix for sure. We do have them tagged here on GitHub.

https://github.com/bordoni/fakerpress/tags

[joe4dev]

Great, meanwhile wp plugin install https://github.com/bordoni/fakerpress/archive/0.2.2.zip would be a workaround according to http://wp-cli.org/commands/plugin/install/

[bordoni]

Just one question, why would rather have an older version of the plugin? Something I've changed?

[joe4dev]

I'm working on a Wordpress benchmark for our research tool Cloud WorkBench and want provide reproducibility (lock version).
I've written a Ruby client therefore which I've adapted for 0.3.x but it might break on future versions.

[bordoni]

Very cool solution @joe4dev! In the future I intend to create a wp-cli Add-on to FakerPress, to allow this kind of benchmarking tools to be faster.

[bordoni]

Moved this out of the release, since it's not a code thing. It's more of adding the zips there.