There is an easy way to debug this, you create a composer.json containing your repository, i.e.:
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/Luracast/Restler"
}
]
}
Then you run composer show -v luracast/restler
, the -v will display details when parsing the git repo. The output of this command is:
Reading composer.json of luracast/restler (3.0.0-RC1)
Skipped tag 3.0.0-RC1, tag (3.0.0.0-RC1) does not match version (3.0.0.0) in composer.json
Reading composer.json of luracast/restler (3.0.0)
Importing tag 3.0.0 (3.0.0.0)
Reading composer.json of luracast/restler (2.2.0)
Skipped tag 2.2.0, no composer file
Reading composer.json of luracast/restler (1.0.20)
Skipped tag 1.0.20, no composer file
Reading composer.json of luracast/restler (features/AOP)
Importing branch features/AOP (dev-features/AOP)
Reading composer.json of luracast/restler (features/forms)
Importing branch features/forms (dev-features/forms)
Reading composer.json of luracast/restler (features/html)
Importing branch features/html (dev-features/html)
Reading composer.json of luracast/restler (features/oauth)
Importing branch features/oauth (dev-features/oauth)
Reading composer.json of luracast/restler (features/router)
Importing branch features/router (dev-features/router)
Reading composer.json of luracast/restler (features/swagger1.2)
Importing branch features/swagger1.2 (dev-features/swagger1.2)
Reading composer.json of luracast/restler (master)
Importing branch master (dev-master)
Reading composer.json of luracast/restler (v1)
Skipped branch v1, no composer file
Reading composer.json of luracast/restler (v2)
Skipped branch v2, no composer file
Reading composer.json of luracast/restler (v3)
Importing branch v3 (3.x-dev)
name : luracast/restler
descrip. : Restler is a simple and effective multi-format Web API Server framework written in PHP. Just deal with your business logic in php, Restler will take care of the REST!
keywords : server, api, framework, REST
versions : dev-master, 3.x-dev, v3.0.0, dev-features/swagger1.2, dev-features/AOP, dev-features/forms, dev-features/oauth, dev-features/html, dev-features/router
As you see, tags have been skipped because they are missing a composer.json or the version didn't match (I see you removed the version in the master branch, that's the right thing to do). Only one tag (3.0.0) was imported successfully and shows up in the second bit of output in the list of versions.
So in other words, all is well and new tags you create from the master branch should show up without problems on packagist, along with the 3.0.0 which is already there.