Repository navigation
fix: prepare PyPI-compatible umf-tablespec 0.0.14 - #42
Merged
Merged
Conversation
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
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.
The immutable
v0.0.13artifacts declare a direct Git URL forumf-core, which PyPI rejects. This successor pins the same core release asumf-core==0.10.0, now published on PyPI. The PyPI sdist’ssrc/umffiles and project metadata match pinned UMF commit4cdddceaceded64e59ac24b65f106e9610f90653; per-file hashes and PyPI artifact hashes are recorded indocs/helix/04-build/evidence/umf-core-0.10.0-pypi-source-match-2026-10-27.json.The package lock resolves core from PyPI, install guidance uses the public version, and plugin manifests plus publication fixtures advance to
0.0.14. The built wheel and sdist both identifyumf-tablespec==0.0.14, requireumf-core==0.10.0, and contain no direct URL/SCM requirements.Validation:
tests/unit/test_pypi_publication.py(2 passed), Ruff on that test,uv lock --check, artifact metadata checks for wheel and sdist, release-manifest creation check, and diff/JSON validation. No macOS CI was run.