Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
composer /
faqs /
Delete
Unzip
Name
Size
Permission
Date
Action
how-do-i-install-a-package-to-a-custom-path-for-my-framework.md
2.17
KB
-rw-r--r--
2023-03-21 10:50
how-to-install-composer-programmatically.md
1.41
KB
-rw-r--r--
2023-03-21 10:50
how-to-install-untrusted-packages-safely.md
2.18
KB
-rw-r--r--
2023-03-21 10:50
should-i-commit-the-dependencies-in-my-vendor-directory.md
1.67
KB
-rw-r--r--
2023-03-21 10:50
which-version-numbering-system-does-composer-itself-use.md
153
B
-rw-r--r--
2023-03-21 10:50
why-are-unbound-version-constraints-a-bad-idea.md
1.04
KB
-rw-r--r--
2023-03-21 10:50
why-are-version-constraints-combining-comparisons-and-wildcards-a-bad-idea.md
989
B
-rw-r--r--
2023-03-21 10:50
why-cant-composer-load-repositories-recursively.md
2.06
KB
-rw-r--r--
2023-03-21 10:50
Save
Rename
# Why are unbound version constraints a bad idea? A version constraint without an upper bound such as `*`, `>=3.4` or `dev-master` will allow updates to any future version of the dependency. This includes major versions breaking backward compatibility. Once a release of your package is tagged, you cannot tweak its dependencies anymore in case a dependency breaks BC - you have to do a new release, but the previous one stays broken. 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 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). **Note:** As a package maintainer, you can help your users by providing an [alias version](../articles/aliases.md) for your development branch to allow it to match bound constraints.