[CHORE](pyspark) Baseline overture-schema-pyspark to a static 0.1.1 version - #589
Merged
Merged
Conversation
overture-schema-pyspark was missed by the Phase 2.A version baselining (#534) and the follow-up that dropped the __about__.py shims (467a550): it still declared a dynamic hatchling version backed by a __about__.py pinned at 0.1.0, out of step with the twelve sibling packages now on a static 0.1.1. Replace the dynamic version with a static version = "0.1.1" and remove the orphaned __about__.py, matching overture-schema-system. Aligning the version also lets the Phase 2.B release-bump detector parse every package's pyproject.toml, which it currently cannot for pyspark. Signed-off-by: Seth Fitzsimmons <seth@mojodna.net>
🗺️ Schema reference docs preview is live!
Note ♻️ This preview updates automatically with each push to this PR. |
Victor Schappert (vcschapp)
approved these changes
Jul 22, 2026
Roel Bollens (RoelBollens-TomTom)
self-requested a review
July 23, 2026 15:26
Roel Bollens (RoelBollens-TomTom)
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
overture-schema-pysparkwas the one package that slipped through the Phase 2.A version-baselining cleanup. It still declareddynamic = ["version"]backed by a[tool.hatch.version]shim (__about__.pypinned at0.1.0), while its twelve sibling packages were converted to a staticversionand had their shims deleted (#534 / e36655d, then 467a550). This makes pyspark consistent with them.Changes
packages/overture-schema-pyspark/pyproject.toml: replacedynamic = ["version"]withversion = "0.1.1"and remove the[tool.hatch.version]block, matchingoverture-schema-system.packages/overture-schema-pyspark/src/overture/schema/pyspark/__about__.py.uv.lock: re-resolved; recordsoverture-schema-pysparkat0.1.1.0.1.0->0.1.1is a patch alignment to the shared baseline. The minor is unchanged, so this does not trigger a release.Why now
Aligning the version also unblocks the Phase 2.B release-bump detector in #557:
detect_version_bumps.pyreads["project"]["version"]from everypackages/*/pyproject.toml, which raisesKeyErroron pyspark's dynamic declaration and fails the detect step for all packages.Closes #588