Untagged Plugins

WordPress officially recommends tagging every release in SVN and is working on disabling trunk as a release mechanism. Until then, these plugins can be installed via dev-trunk but can't be pinned to specific versions.

If you depend on one of these plugins, the best path forward is to ask the plugin author to tag their releases in SVN. It takes one command and makes the version available for Composer installs. See issue #15 for more details.

If you're using WPackagist, be aware that WPackagist serves mutable trunk zips for untagged plugins, meaning your installed version can change between installs even with a lock file. This can result in unexpected plugin updates. WP Packages pins untagged installs to a specific SVN revision, so your lock file is always reproducible. If you're still on WPackagist, consider migrating to WP Packages.