linkml/schema-automator: v0.5.7

Released alongside linkml-map 0.5.4, and validated downstream against dm-bip before tagging.

Changes

Require linkml-map 0.5.4 (#220, #224) 0.5.4 drops linkml-map's requires-python < 3.14 cap. That cap was why pip install schema-automator failed on Python 3.14 even though we advertise >=3.10 and test 3.14 in CI — our own CI only passed because uv sync installs from the lock, which doesn't enforce a dependency's Requires-Python. Downstream consumers resolve fresh, so they hit it. Verified with a fresh 3.14 resolve from a built wheel, no lock involved.

Import SchemaBuilder from linkml_runtime (#221) linkml deprecated the linkml.utils.schema_builder re-export in 1.11 and removes it in 1.12, which our linkml < 2 pin would pick up. Migrated 8 modules and 4 tests. The two paths resolve to the same object today, so behaviour is unchanged, and no pin bump is needed — linkml_runtime.utils.schema_builder has carried the full API since 1.10.0, our declared floor. This is the PyPi package published from the mono-repo not the linkml/linkml_runtime repo that has been archived.

Fix PyPI publishing (#222, #223) The publish workflow triggered on release created, which never fires for draft releases — and the GitHub UI drafts by default, so the normal draft-then-publish flow never published. Now triggers on published, with workflow_dispatch as a manual retry hatch. Also bumps pypa/gh-action-pypi-publish to v1.14.2, whose Twine v7 accepts the Metadata-Version: 2.5 that current hatchling emits.

Notes

pip install schema-automator now works on Python 3.14 from a fresh resolve, not just from the lock.

Released from v0.5.7-rc2, which was published to PyPI and exercised in dm-bip. The only change since is the linkml-map floor moving from >= 0.5.4rc1 to >= 0.5.4.