What are you trying to do?
Currently, only the package version is part of the path name. The actual reference hash is not. This causes issues if the version is rewritten (can, but should not happen) or if a branch is used (not that uncommon for development packages, especially internal ones)
What feature or behavior is this required for?
Download the exact version that is required from the composer.lock as referenced by the hash, not the package version
How could we solve this issue? (Not knowing is okay!)
Rewrite all URLs so that the reference hash is used instead of the package version.
For example, if I require elendev/nexus-composer-push from packagist, the download url is <github-url>/repos/Elendev/nexus-composer-push/zipball/9dc7d473eb0f28adb5caf829575b90d3010a59af.
While the same requirement using this plugin currently yields <repository-url>/elendev/nexus-composer-push/0.1.3/elendev-nexus-composer-push-0.1.3.zip
What are you trying to do? Currently, only the package version is part of the path name. The actual reference hash is not. This causes issues if the version is rewritten (can, but should not happen) or if a branch is used (not that uncommon for development packages, especially internal ones)
What feature or behavior is this required for? Download the exact version that is required from the composer.lock as referenced by the hash, not the package version
How could we solve this issue? (Not knowing is okay!) Rewrite all URLs so that the reference hash is used instead of the package version. For example, if I require elendev/nexus-composer-push from packagist, the download url is
<github-url>/repos/Elendev/nexus-composer-push/zipball/9dc7d473eb0f28adb5caf829575b90d3010a59af. While the same requirement using this plugin currently yields<repository-url>/elendev/nexus-composer-push/0.1.3/elendev-nexus-composer-push-0.1.3.zip