Publish project URLs and the current spec version in package metadata - #279
Merged
Conversation
…adata homepage/repository were not valid PEP 621 project keys, so hatchling dropped them from the wheel metadata and the PyPI page would have had no links; the sdist exclude list was similarly inert. The npm manifest's slackblocksSpecVersion still said 1.0.0; the conformance suite now pins it to the shared spec version.
nicklambourne
added a commit
that referenced
this pull request
Aug 17, 2026
…adata (#279) homepage/repository were not valid PEP 621 project keys, so hatchling dropped them from the wheel metadata and the PyPI page would have had no links; the sdist exclude list was similarly inert. The npm manifest's slackblocksSpecVersion still said 1.0.0; the conformance suite now pins it to the shared spec version.
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
1 participant
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.
Scope
Final pre-release audit findings, both irreversible-after-publish:
homepage/repositorysat as bare[project]keys (not PEP 621) so hatchling silently dropped them — the 2.1.0 PyPI page would have rendered without repository/homepage/docs links; a proper[project.urls]table fixes it (and the equally inertexcludenow lives in its real hatch sdist location). The npm manifest's informationalslackblocksSpecVersionstill said 1.0.0 while the runtime/spec agree on 1.0.1; bumped, and the TypeScript conformance suite now asserts the field so it cannot go stale again.Validation
Wheel METADATA now carries four Project-URL entries; strict twine check passes; sdist drops test/ and docs/; TypeScript typecheck + 291 tests green.