Skip to content

fix: prepare PyPI-compatible umf-tablespec 0.0.14 - #42

Merged
easel merged 1 commit into
mainfrom
codex/pypi-v0.0.14
Oct 28, 2026
Merged

easel merged 1 commit into
mainfrom
codex/pypi-v0.0.14

Conversation

@easel

@easel easel commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

The immutable v0.0.13 artifacts declare a direct Git URL for umf-core, which PyPI rejects. This successor pins the same core release as umf-core==0.10.0, now published on PyPI. The PyPI sdist’s src/umf files and project metadata match pinned UMF commit 4cdddceaceded64e59ac24b65f106e9610f90653; per-file hashes and PyPI artifact hashes are recorded in docs/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 identify umf-tablespec==0.0.14, require umf-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.

@easel
easel merged commit b88bf7a into main Oct 28, 2026
3 checks passed
@easel
easel deleted the codex/pypi-v0.0.14 branch November 2, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant