-
-
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
Tilde/Caret versioning range and specifying the stability like ^x.y.*-dev #11881
Comments
This page: https://getcomposer.org/doc/articles/versions.md#stability-constraints |
Thanks for your response @fredden EDITED: The issue appears when I run: composer require internalvendor/user-module:^1.0-dev The command above finds and picks the latest version of package (let's say 1.2.0), but totally ignores |
@Seldaek Don't you have any idea ? Seems to be a weird one. |
@arfar-x I can see that you have closed this issue. Are we to understand that you have found all the answers you were seeking? Please can you post some details here or a link to the documentation where you found the answers? This will help others who might be having a similar issue. Or perhaps this was closed by mistake, and the issue is not yet solved? |
The issue is not resolved yet. What details should I provide exactly ? I've already provided information I thought it would be useful. |
Hello there,
I'm using a private registry named Nexus for my company's internal packages. The scenario is I store different package stability for each version. I.e. for v1.0.0 I have
1.0.0
,1.0.0-rc
, and1.0.0-dev
. Additionally, the repository type I have used for this private registry is set ascomposer
. Therefore, I don't have any of my Git tags and I have to handle the versions by packages names and the URLs.Here is how I store packages and its works well:
Here is a detailed information of how my versions are.
So the question is:
How can I specify the version range to install the latest version of each package with the desired stability ?
I want something like this:
The text was updated successfully, but these errors were encountered: