Create tag alias 2.1.1 for dev-master #74

wants to merge 1 commit into


None yet
5 participants

For current use in composer as

"hybridauth/hybridauth": "2.1.*"

spiffyjr commented Feb 8, 2013

Yes, please. We need aliases or tagging.

+1 I don't like including code tagged as non-stable in production releases, and this 2.1.x version seems to be stable for now.

EDIT: Though it would probably be better to create a git tag, as packagist will automatically pick that up. Including aliases in the composer.json is rather hackish IMHO.

@StorytellerCZ StorytellerCZ added this to the 2.2.x milestone Feb 17, 2014


StorytellerCZ commented Feb 17, 2014

We will be using the Github tags.


SocalNick commented May 21, 2014

@adwintrave can we tag something (latest master) as 2.1.0 if it is stable? It doesn't need to be perfect, it just needs to work. Any bug fixes can continue in 2.1.x and be merged into 2.2.x.


StorytellerCZ commented May 25, 2014

@SocalNick Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment