Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add version tags for composer #10

Open
davidgorges opened this issue Feb 26, 2015 · 5 comments
Open

Add version tags for composer #10

davidgorges opened this issue Feb 26, 2015 · 5 comments

Comments

@davidgorges
Copy link

Please add a version tag to the repository. That would allow us to require that specific version in composer. Right now we are forced to use dev-master.

@mablae
Copy link

mablae commented Feb 7, 2016

👍

@PowerKiKi
Copy link

That would be nice to have a 1.0.0. released so we don't need to pin on specific commits. Any news on that ?

@digilist
Copy link

would be nice for me too.

@njam
Copy link

njam commented Dec 2, 2016

Not having a version makes it very difficult to use this module in composer. It's stability level is "dev", which means you have to change your "minimum stability".

To create a version you would just need to create a tag and push it to github. Then it will show up on packagist.

@mikeemoo could you create a tag with the current version?
e.g.:

git tag 0.1.0 361b8a8727d13b67cb593a936a715ad2204ececb
git push --tags

@jpuck
Copy link

jpuck commented Jan 30, 2017

Awesome that the 1.0.0 tag was released, but the packagist repository hasn't been updated with the tag, so composer still can't resolve the minimum stability as stable

Packagist is supposed to periodically crawl the repos for updates, but it apparently hasn't done so it almost a year. Probably best to setup a Github service hook.

jpuck added a commit to MyTeamName/color-contrast-php that referenced this issue Jan 30, 2017
per mikeemoo/ColorJizz-PHP#10

despite having added the 1.0.0 release, packagist still has not
crawled the repository to reflect the available stable version.

manually adding the Github repo as a vcs repository to composer.json
should actually speed things up for resolution on installation and
guarantee new release tags are picked up.

the only drawback would be if @mikeemoo deleted the repository from
Github all together. Github forwards transfers, so that shouldn't
break it either.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants