Composer - The requested package exists as but these are rejected by your constraint

Composer - The requested package exists as but these are rejected by your constraint

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Composer - The requested package exists as but these are rejected by your constraint

When you encounter the message The requested package antoineb1/smoney_bundle 1.0 exists as antoineb1/smoney_bundle[dev-master] but these are rejected by your constraint, it is a classic conflict between semantic versioning expectations and the reality of how Version Control Systems (VCS) handle tags. You are telling Composer to install a specific version tag (1.0), but the repository only exposes a development branch labeled dev-master.

In your composer.json, you have defined "minimum-stability": "dev" and set "prefer-stable": true. This configuration tells Composer to look for stable releases first, but if none exist, it will accept dev versions. However, the error message reveals that the package antoineb1/smoney_bundle does not actually have a tag named 1.0. Instead, the repository provides a branch named dev-master.

Composer treats tags and branches as distinct entities when resolving version constraints. A constraint of ^1.0 or simply 1.0 expects a Git tag exactly matching that string. When Composer queries the VCS repository (in your case, BitBucket) for a tag 1.0, it returns nothing. It then looks at available branches and finds dev-master. Because your constraint explicitly asks for 1.0 and not dev-master, Composer rejects the branch as a match for that specific string literal.

The immediate fix involves adjusting the version constraint in your require section to point directly to the branch name rather than a non-existent tag. You should change:

"antoineb1/smoney_bundle": "1.0"

To:

"antoineb1/smoney_bundle": "dev-master"

Alternatively, if you want to allow Composer to resolve to any branch that matches the semantic versioning logic of 1.0, but knowing that no tags exist, you might need to explicitly accept dev stability for this specific package without relying on a tag match. However, the cleanest approach with a VCS repository that lacks proper release tags is usually to point directly to the desired branch name.

There is also a warning in your output regarding Xdebug: You are running composer with xdebug enabled. While not the cause of the resolution error, this is significant because Composer itself runs code during dependency resolution. If Xdebug is active, this process can be drastically slower than necessary. For production environments or CI pipelines where you are installing dependencies for the first time, it is best practice to disable Xdebug before running composer install. You can check your environment variables or your IDE settings to ensure Xdebug is not inadvertently enabled during the build process.

Your configuration includes a VCS repository definition pointing to a BitBucket URL. This is necessary because the package is not available on Packagist. When using external repositories, it is crucial that the package adheres to the composer.json structure within that repository itself. The error implies that the remote repository does not have a tag matching your request. If the maintainer of antoineb1/smoney_bundle intended version 1.0 to be released but simply forgot to create a Git tag, they must create one using a command like:

git tag -a 1.0 -m "Release version 1.0"
git push origin 1.0

Once that tag exists in the remote repository, your original constraint "antoineb1/smoney_bundle": "1.0" will work correctly without needing to reference dev-master. Until then, treating the package as a dev dependency by referencing the branch directly is the only viable path forward for resolving the installation.

Our network