Dev Branches Keep Multiple Versions

[john-everden]

When using branch based commits for reference for instance

composer require namespace/package:dev-my-branch

I've noticed packeton only keeps a reference to the latest commit on "my-branch" in this instance. Lock files will lock to the specific commit on this branch. This causes a not found error when attempting to run composer install if a later commit has been pushed as packeton only keeps the very latest commit for download. I've only ever used dev branches within packeton and I'm uncertain if this is a limitation of the this specific software package or composer in general. If it's a limitation of the software is this configurable somewhere or possible to change? It makes it inconvenient for the team I'm working on as we have composer install running on container startup and the containers will crash loop when it fails to install the missing prior commit referenced in the lock file.

[vtsykun]

Hi @john-everden
This bug was fixed here #51

I did a quick test on demo https://demo.packeton.org/packages/composer/composer#dev-main to check and it seems to work correctly

1. Current dev-main ref https://demo.packeton.org/zipball/composer/composer/8e62977cb5de315d5190c021a2b2bb4e59ee2f4f.zip
2. HEAD~1 https://demo.packeton.org/zipball/composer/composer/6198fc1053ede6af9b401a75f4badf0311d2adc1.zip