packagist: packagist not detecting version of my package
https://packagist.org/packages/jurchiks/numbers2words
When I initially added the package, the composer.json file did not contain version info and there was no version tag, but the command composer require jurchiks/numbers2words did not work and continues to not work:
[InvalidArgumentException]
Could not find package jurchiks/numbers2words at any version for your minimum-stability (stable). Check the package spelling or your minimum-stability
Since adding the package, I have added a github push hook, pushed a “version”: “1.0.0” addition to the repository, upped the version to 1.0.2, added a git tag 1.0.0 and deleted the “version” entry in composer.json file. I’ve tried deleting the version shown on the package page and manually updating it.
Nothing helps! It is still detecting only dev-master.
WTF? What does it want from me?
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 39 (18 by maintainers)
Commits related to this issue
- Removed version from composer.json (see composer/packagist#587) — committed to balazscsaba2006/craft3-cookiebot by balazscsaba2006 6 years ago
Can you perhaps stop the complaining and explain what the problem is? Of the 70 thousand packages we have on packagist, you’re the first person ever to complain about having to
git tagto release.there is an known issue with github hooks: pushing a tag pointing to a commit which is already available on Github (and so not pushing any new commit) does not trigger the
pushwebhook, and so Packagist is not notified. The workaround is to trigger a manual update in the packagist UI. Otherwise the tag will be picked only the next time you push a commit to github.And I strongly recommend you not to add an explicit version in your composer.json: if you have an explicit version in your file and it does not match the tag name, Composer will consider the tag as broken and will reject it (and it will never appear on Packagist because of that).
What you want does not say why you want it. Anyway no that’s not gonna be possible, but if you explained then maybe just maybe we can find a better way.
defective system. F#@$ing slowpoke. lose 12 hours of working time just because no one is able to describe it in the instructions. So write: The system is flawed, finished the work? Wait a day until the result comes to Packagist. Fine. Wonderful.
@alcohol yes, that works after 12 hours since i push it to github 😃 thats why i posted here. I dont know what happen with github or packagist but that was strange
Hi, im googling for this and my issue is a little bit different. i have a repository eghojansu/fa-simple-php which i have already set a webhooks to packagist fa-simple-php. Now my package version is 2.2.1 but still when i use
composer create-project eghojansu/fa-simple-php, i am getting previous version (2.1.2).I already create new tag (2.2.1 is same as 2.2.0). and I already clear composer cache. this Issues still appear. what should i do? please help
PS: sorry for my bad english
I just usually do
git push && git push --tagson the command line.@jurchiks if you push the master branch first, and then push the tag later in a separate command, github will notify a
pushwebhook for the first push updating the branch (but the tag does not exist yet on Github so Packagist cannot see it) and will not notify it for thegit push --tagscommand following it (because it is not pushing any commit)Yeah, I read about that mismatch thing and that’s why I removed it, but that didn’t solve the issue, even though I tried manually removing the versions and updating the package.
This isn’t an issue with the github hook per se. It should have detected the version right when I added “version”: “1.0.0” to
composer.json, the push hook worked because the last update time changed on the package page, but the version was not detected.I would much rather just update the version in the composer.json whenever necessary than do the tagging, simply because it is simpler that way.