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

Stable dependencies in composer.json instead of "dev-master" #30

Closed
bvis opened this issue Aug 3, 2015 · 4 comments
Closed

Stable dependencies in composer.json instead of "dev-master" #30

bvis opened this issue Aug 3, 2015 · 4 comments

Comments

@bvis
Copy link

bvis commented Aug 3, 2015

Hi,

I've seen that in your dependencies list you have them defined as:

"require": {
    "php": ">=5.3.0",
    "guzzlehttp/guzzle": "~5.0",
    "ext-json": "*",
    "adoy/oauth2": "dev-master",
    "firebase/php-jwt" : "~2.2"
  },

The "adoy/oauth2" component has stable version 1.2.0: https://packagist.org/packages/adoy/oauth2

Is it there any reason to use the "dev-master" instead the stable version?

As you may know rely on development dependencies makes your software so fragile and it can break at any time after a "composer update" execution.

My suggestion is to update this component version to: "adoy/oauth2": "~1.2"

Regards,

@glena
Copy link
Contributor

glena commented Aug 3, 2015

Yes, becase the 1.2.0 tags does not have the latest chages (like a PR I sent) so we cant rely on a stable tag.

It is on my plans changing of oauth2 package but right now is not a priority (PRs welcome :D).

Anyway, this dependency is not very active so I doubt a change can break you project. You can always fork the repo and override it on composer (check https://getcomposer.org/doc/05-repositories.md#loading-a-package-from-a-vcs-repository).

@glena glena closed this as completed Aug 3, 2015
@glena
Copy link
Contributor

glena commented Aug 3, 2015

@bvis before you ask, it is 1.0.9 ;)

@bvis
Copy link
Author

bvis commented Aug 4, 2015

Thanks! ;)

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants