Release 5.0.1.19 fails to load via Composer

It appears there was a change in how releases were tagged starting with 5.0.1.19 and it causes a failure when loading the plugin using Composer via wpackagist.org

If you look at your 5.0.1.18 tag at https://plugins.trac.wordpress.org/browser/tansa/tags/5.0.1.18 you see the directory structure

dist/
ClientTexts.xml
readme.txt
settings.php
tansa.php

however when you look at your 5.0.1.19 tag at https://plugins.trac.wordpress.org/browser/tansa/tags/5.0.1.19 you see the directory structure

assets/
branches/
tags/
trunk/

While installing via the WordPress web interface seems to smooth out this difference (by I assuming downloading only the contents of trunk/, when loading via Composer (e.g. composer require wpackagist-plugin/tansa:5.0.1.19) we get the exact content from the tag (assets, branches, etc.) which does not include an executable file in the root directory and therefore does not load.

Reproduction Steps

• Run composer require wpackagist-plugin/tansa:5.0.1.19
• View the contents of the installed tansa directory

Expected: The tansa/ directory contains tansa.php

Actual Behavior: The tansa/ directory does NOT contain tansa.php

Note: If you run composer require wpackagist-plugin/tansa:5.0.1.18 for reference, you’ll see the tansa/ directory does contain tansa.php

Suggested Resolution

Would you please create a 5.0.1.20 tag that includes tansa.php and the associated files with it in the root directory, so the plugin works when installing via Composer.