Every distributable package under packages/* was moved to a static version in its pyproject.toml during Phase 2.A baselining (#534, e36655d), and the now-orphaned __about__.py version shims were deleted in 467a550. overture-schema-pyspark was missed on both counts: it still declares dynamic = ["version"] backed by [tool.hatch.version] reading a __about__.py pinned at 0.1.0, while its twelve sibling packages are static at 0.1.1.
Beyond the plain inconsistency, this breaks the Phase 2.B release-bump detector added in #557. detect_version_bumps.py reads ["project"]["version"] from every packages/*/pyproject.toml; that key does not exist for pyspark's dynamic declaration, so tomllib lookup raises KeyError and fails the whole detect step. Because the detector globs all packages regardless of which one triggered the push, this would block every release, not just pyspark's.
Fix: replace pyspark's dynamic version with static version = "0.1.1" and remove the orphaned __about__.py, matching the sibling packages.
Every distributable package under
packages/*was moved to a staticversionin itspyproject.tomlduring Phase 2.A baselining (#534, e36655d), and the now-orphaned__about__.pyversion shims were deleted in 467a550.overture-schema-pysparkwas missed on both counts: it still declaresdynamic = ["version"]backed by[tool.hatch.version]reading a__about__.pypinned at0.1.0, while its twelve sibling packages are static at0.1.1.Beyond the plain inconsistency, this breaks the Phase 2.B release-bump detector added in #557.
detect_version_bumps.pyreads["project"]["version"]from everypackages/*/pyproject.toml; that key does not exist for pyspark's dynamic declaration, sotomlliblookup raisesKeyErrorand fails the whole detect step. Because the detector globs all packages regardless of which one triggered the push, this would block every release, not just pyspark's.Fix: replace pyspark's dynamic version with static
version = "0.1.1"and remove the orphaned__about__.py, matching the sibling packages.