-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Proposal: adding a composer outdated command #3771
Comments
@jenssegers What does |
I think |
Yes, it shows the current version, highest matching version according to constraints, the latest version you can update to, and it does it for the dependencies of your dependencies too. |
I also would like to see something like this. I thought about starting a pull request, but this gets kinda complex, at least with no knowledge in composer internals. |
👍 |
2 similar comments
+1 |
+1 |
+95 |
i miss this feature a lot! |
You can actually do |
@hannesvdvreken --dry-run does not give information about packages, versions of which are locked at some version. For example, if package has version 2.5.0 and composer.json has ~2.4.4, we will not receive 2.5.0 update. That is what this proposal is about. |
yes please! |
+1 |
This could be easily implemented as a plugin if this was in place: #3377 |
+1 |
+1 This would definitely be a great feature. npm-check-updates does this very well for node packages. $ npm-check-updates
express 4.12.x → 4.13.x
multer ^0.1.8 → ^1.0.1
react-bootstrap ^0.22.6 → ^0.24.0
react-a11y ^0.1.1 → ^0.2.6
webpack ~1.9.10 → ~1.10.5
Run with -u to upgrade your package.json Maybe we could have a similar setup showing installed and the latest available version? |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
In the meantime we can use this package: https://github.com/vinkla/climb It is still in early stages of development but it is a start. |
+1 |
3 similar comments
👍 |
+1 |
+1 |
+1 |
1 similar comment
👍 |
If @vinkla, or one of composer's contributors (or someone else) wants to integrate that into composer and maintain that: great. Just sayin' we can stop |
Any plan? @vinkla is it possible to contribute your work into composer? |
@mtangoo the Climb package wont work in Composer core but it would be nice if the functionality were somewhat similar. |
Ok thanks. Does climb return Json? I don't want to poisone the thread but wanted to know just that |
@mtangoo not right now but it will in the future. If you've any more questions you can open an issue in the Climb repository. |
@Addvilz The |
@schmunk42 that doesn't really affect the problem at hand, does it? No matter how you constrain your deps, you should be able to tell if a new version is available without running to packagist. :) |
I think constraints are an important part to consider here, but I know what you mean. A little helper for the bash...
btw ... if there's an update available, which not matches your constraint, how should it be displayed? |
@schmunk42 Perhaps, that could be managed using command line flags? For example "composer show-outdated --include-dev" would list latest versions including dev-master etc. How I imagine this could work is that the command would show possible minor and patch increments for current major version and also list possible major version increments. Consider the example: Locked version: 1.3.3 This would give ability to decide to which one to update to. Also could be managed via cli switches. Just from top of my head... |
+1 |
So there already is an |
Something like this? #5028 |
Is there an official position on this issue? been waiting for this command for nearly a year now. |
There's PR's with a lot of discussion, it's labeled 'Feature' and 'Nice to Have', what more official position do you want? |
Last we heard was that there was a lot of talk about this but no contributions. But there are now and I will like to know what is the hold up here. |
That the proposed implementation is flawed and that Composer 1.0 is in beta which means no big new features are added. You're welcome to submit a better PR though for after 1.0 final release. |
I was referring to #4517 not doing exactly what is wanted in all situations. There are multiple solutions right now and not really a clear path on which is best yet. |
@adragus-inviqa MY MISTAKE: I didn't read the full thread. I've removed my dummy +1. Thread should be closed if the final position is to use a third-party plugin / tool for this. I think it can help to give my point-of-view regarding such a feature should be justified to be core or not. I'll try to be more productive even if i'm not in my native language. I'm using composer to manage Magento projects (Magento 1 in a home-made environment) and Wordpress based websites using the Bedrock stack (and combination of them). Drawback : i need to check available plugins updates by hand... => That would be cool to have it built-in : listing available updates for every package ignoring fully-qualified versions. I mention it because i think (maybe i'm wrong) that it would not be too hard to implement as composer ALREADY do it if using ^* things. That's my point, comma. => There is a third party solution : climb : great : I'll give a try to climb. End of transmission. Thanks for reading |
|
Thank you @Seldaek |
Hey guys,
When I'm using other package managers, I often use commands like
bower list
ornpm outdated
to find out if packages have a newer release, and can be upgraded. However, composer is kind of lacking this functionality. There is the possibility to run the update with the--dry-run
option, but that will not tell you if there is a newer version if you have strict versions incomposer.json
.Is this something that could be on the roadmap?
The text was updated successfully, but these errors were encountered: