Only stable release (0.1.0) is yanked with no replacement, blocking plexosdb>=1.6.0

[elasticdotventures]

Summary

plexosdb 1.6.0 (current PyPI release) depends on plexos2duckdb>=0.1.0b11. The only version of plexos2duckdb at or above that bound that isn't a pre-release is 0.1.0 — and it's yanked from PyPI:

plexos2duckdb==0.1.0 was yanked (reason: this version doesn't contain any binaries and should not be used)

That leaves no non-prerelease version satisfying plexosdb's own requirement. A clean-room uv pip install plexosdb (or anything depending on plexosdb>=1.6.0, e.g. r2x-plexos>=0.3.0) fails outright without explicitly forcing prerelease resolution (--prerelease=allow), which most downstream consumers' tooling doesn't do by default.

Ask

Cut a new stable release (e.g. 0.1.1 or 0.2.0) that actually contains binaries, so plexos2duckdb>=0.1.0b11 is satisfiable without opting into prereleases. Currently the only installable versions are the pre-0.1.0b11 betas or the yanked 0.1.0.

Context

Hit this while pulling in plexosdb/r2x-plexos for a downstream connector (Power-Agent/PowerMCP#53) — reproduced with a fresh venv, no other installed packages involved:

$ uv pip install "r2x-plexos==0.3.0"
× No solution found when resolving dependencies:
  ╰─▶ Because plexos2duckdb==0.1.0 was yanked (reason: this version doesn't
      contain any binaries and should not be used) and only the following
      versions of plexos2duckdb are available:
          plexos2duckdb<0.1.0b11
          plexos2duckdb>=0.1.0
      we can conclude that plexos2duckdb>=0.1.0b11 cannot be used.
      And because plexosdb==1.6.0 depends on plexos2duckdb>=0.1.0b11 ...