public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

docs: Fix inconsist semver operator suggestion (#10810) 

Using caret over tilde is better since it behaves the same as in npm:
https://jubianchi.github.io/semver-check/#/constraint/~3.0
But when this change was introduced in https://github.com/composer/composer/pull/5396,
it was not complete.
pull/10811/head^2
Jan Tojnar 2022-05-31 13:24:38 +02:00 committed by GitHub
parent 5d353716d3
commit 955194f896
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/faqs/why-are-unbound-version-constraints-a-bad-idea.md
View File

@ -12,7 +12,7 @@ The only good alternative is to define an upper bound on your constraints,
which you can increase in a new release after testing that your package is
compatible with the new major version of your dependency.
For example instead of using `>=3.4` you should use `~3.4` which allows all
For example instead of using `>=3.4` you should use `^3.4` which allows all
versions up to `3.999` but does not include `4.0` and above. The `^` operator
works very well with libraries following [semantic versioning](https://semver.org).