composer/composer — Issue #169: Update when master branch has changed (but version has not)
Author: ddeboer
Created: 2011-12-22 14:33:37+00:00
State: open

Right now a package is only updated when a new version is available. However, entries in the `composer.json` that follow the master branch (so have `master-dev` for required version), are not updated after a new commit has been pushed to that master branch.

Of course, Composer is primarily meant to track new versions. Would it be possible, however, to allow tracking commits, too? It seems that `packages.json` for http://packagist.org is already updated when a new commit has become available. The commit hash in the `packages.json` could then be compared to the commit that is installed locally, and the local clone be updated if necessary.