IonBazan / composer-diff

Compares composer.lock changes and generates Markdown report so you can use it in PR description.

Home Page:https://packagist.org/packages/ion-bazan/composer-diff

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Upgrading one dev version to another may produce duplicate entry

IonBazan opened this issue · comments

After upgrading rector/rector from 0420629 to 2e028e5 (dev-main), composer diff produced following output:
image

             "source": {
                 "type": "git",
                 "url": "https://github.com/rectorphp/rector.git",
-                "reference": "04206292794cdf1932d3c8d7ce1ed139d69039fd"
+                "reference": "2e028e5734f34f4afeb34e8b8c2da021b731760a"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/rectorphp/rector/zipball/04206292794cdf1932d3c8d7ce1ed139d69039fd",
-                "reference": "04206292794cdf1932d3c8d7ce1ed139d69039fd",
+                "url": "https://api.github.com/repos/rectorphp/rector/zipball/2e028e5734f34f4afeb34e8b8c2da021b731760a",
+                "reference": "2e028e5734f34f4afeb34e8b8c2da021b731760a",
                 "shasum": ""
             },

While version constraint didn't change, it should produce only a single "change" row instead of "update" and "change".

This might be caused by the branch alias though.