update to package marked as '--dev'

[Scott Wood]

down votefavorite

I recently took 'ownership' of a git repository for some code made for my company by a third party. I finally needed to update something in the package yesterday and realized I also needed ownership of the packagist package details. Upon contacting the developer, he just removed his version of the libraries on packagist and I re-created them from my own account. It seems to work fine for the existing code, but now I'm trying to update it. I made the updates on github, added tags for both v0.0.6 and 0.0.6 and pushed a new branch "0.0.6" then updated packagist.

But it shows up with 0.0.6.x-dev

And our live site is set not to accept development branches (and the staging branch is configured to match live) so composer won't download the update.

I've checked a number of threads and while I see many references to the fact packagist defaults to -dev on new branches, I have yet to find any instructions on how to change the default or otherwise change the branch to be non-dev.

What is the correct process for posting a non-dev update to packagist?

[Jordi Boggiano]

The correct process is to create a git tag. Branches are always dev. Tags are always stable/beta/alpha/RC depending on the tag name.

See also https://getcomposer.org/doc/articles/versions.md#composer-versions-vs-vcs-versions

And by the way you don't need to tag v0.0.6 *and* 0.0.6, one of them will suffice for composer as it normalizes both to the same anyway.

Best,
Jordi

--
You received this message because you are subscribed to the Google Groups "composer-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to composer-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
Jordi Boggiano
@seldaek - https://seld.be

[Scott Wood]

OK, I added a tag 'stable' and pushed it both as master and as 0.0.6, clicked update in packagist and nothing changed. (no 0.0.6, still just a 0.0.6-dev).
So then I tried pushing it as 0.0.6-stable with the same tags and I get a new one as 'dev-0.0.6-stable'

Now what?

[Jordi Boggiano]

You should add a "0.0.6" tag. Also if you want help at least give your package's name/URL, otherwise I'm just guessing at what you mean.

Best,
Jordi

[Scott Wood]

I had both but for some reason it didn't work. I tried updating the version as well as the tags and it seemed to work but it created both a 0.0.7 and a 0.0.7-dev at the same time in packagist from a single push