Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
how-do-i-install-a-package-to-...	2.17 KB	-rw-r--r--
how-to-install-composer-progra...	1.4 KB	-rw-r--r--
how-to-install-untrusted-packa...	1.39 KB	-rw-r--r--
should-i-commit-the-dependenci...	1.67 KB	-rw-r--r--
which-version-numbering-system...	153 B	-rw-r--r--
why-are-unbound-version-constr...	1.04 KB	-rw-r--r--
why-are-version-constraints-co...	989 B	-rw-r--r--
why-can't-composer-load-reposi...	2.06 KB	-rw-r--r--

Code Editor : why-are-unbound-version-constraints-a-bad-idea.md

# 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.

${this.title}

Code Editor : why-are-unbound-version-constraints-a-bad-idea.md