-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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 update restriction by date #10437
Comments
Technically feasible yes, you can hack this up yourself like this:
Hooked up with this in composer.json:
Just make sure the Foo class is autoloadable by your composer.json autoload rules, then you should be good to go. I don't really think this is a common enough need to justify an additional flag though, and messing with the package pool in this way will void warranty to some extent, it may lead to weird error messages being reported if dependency resolution fails, but as long as it finds a solution with the older packages this should work. |
I'm not sure I'm following. I don't want to update composer.json. I just want to put a limit on which packages are updated at the particular time I run |
Yes, you would add this temporarily to your composer.json to modify composer so it runs the way you want, and then you remove this again from composer.json when you're done. |
Part of the underlying motivation for me filing #10436 was because I am in the middle of an update process that I had to put down for a while, and in the interim new versions of packages have been released. Because I know which versions are new, I am able to exclude them via
--with
.However, it would be wonderful if composer were able to do all this for me, given a particular timestamp. I see that composer.lock has a
time
field, so I presume the data to do this is at least somewhat available.I'm thinking something along the lines of:
Is this doable?
The text was updated successfully, but these errors were encountered: