Bower dependency resolution for incompatible semver constraints

Flat Dependency Tree Constraints

Bower (v1.x) utilizes a flat dependency tree, which restricts the project root to a single version of any given package. This architecture requires all packages in the dependency graph to converge on a version that satisfies every semantic versioning (semver) constraint defined in the respective bower.json files.

Resolution Uncertainty

A technical challenge arises when two top-level dependencies require the same sub-dependency but specify mutually exclusive version ranges. Because Bower cannot isolate these versions into separate nested directories, the installation process must either resolve the conflict based on a specific priority or halt.

What is the documented behavior for resolving a conflict when two dependencies require incompatible versions of a shared library? Is there a mechanism within the root bower.json to force a specific version that overrides these nested constraints?