Packagist.org AutoUpdate Hook about mongodm HOT 3 CLOSED

I have added this hook for a long time. I don't know why the lastest release haven't been updated in packagist yet,may be cache.

from mongodm.

The same issue at composer/packagist#200
The reason is our package version in composer.json is 1.2.0 , not 1.4.0 as release is.
So I redraft a release for v1.4.0.

It will never show a version 2.0.0 for a branch. If you want to have a stable version, you have to create a tag in the repo.
Btw, you should omit the explicit version in your composer.json as it is useless when using a VCS repo but can be harmful. Here is how the version is infered from the git metadata:
for branches, it will be 2.1.x-dev for the branch 2.1 or 2.1.x (same for any branch looking like a version number, to have a comparable version) and dev-master for master (same for any other branch). In these cases, the version field in the composer.json is ignored entirely
for tags, the version is taken from the tag name. If the tag name cannot be parsed as a version, the tag is skipped and cannot be installed through composer. If you specify the version explicitly and it is different than the tag name, the tag will also be considered as invalid and be skipped.
So specifying the version explicitly in a git repo (or a SVN or Hg repo btw) is only a way to make mistakes each time you do a release.

from mongodm.

Good to know thanks!

from mongodm.