fix: move homepage/repository to [project.urls] for PEP 621 compliance#9
Merged
Merged
Conversation
setuptools rejects homepage and repository as top-level [project] keys. Move them to the standard [project.urls] table so `poetry build` succeeds in CI. Signed-off-by: sfph <selina@cisco.com> Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
homepageandrepositoryfrom top-level[project]keys to[project.urls]tableprojectmust not contain {'repository', 'homepage'} propertiesContext
The
v0.2.3tag triggered the publish workflow butpoetry buildfailed because setuptools rejected the invalid keys. The package was never uploaded to PyPI, sov0.2.3can be re-tagged after this merges.After merge
git tag v0.2.3 && git push origin v0.2.3Made with Cursor