Both published packages required build_support/dependency_sources.exs from a
path outside their tarball, so mix compile in any consuming project died while
Mix loaded the dependency's project. 0.2.1, 0.2.2 and 0.1.1 are retired.

mix.exs now detects whether it is running inside the workspace checkout. In the
checkout the dependency-source registry resolves siblings path-first exactly as
before; anywhere else the Hex requirement stated in mix.exs is the whole answer
and build_support is never touched.

Verified by extracting each built tarball outside any workspace and confirming
mix.exs loads and declares only Hex packages, then by compiling both from Hex
in a clean consumer project.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>