Skip to content

Move metadata from setup.py to pyproject.toml - #200

Merged
gforcada merged 1 commit into
masterfrom
convert-setup-py-to-pyproject-toml
Sep 8, 2026
Merged

Move metadata from setup.py to pyproject.toml#200
gforcada merged 1 commit into
masterfrom
convert-setup-py-to-pyproject-toml

Conversation

@gforcada

@gforcada gforcada commented Aug 8, 2026

Copy link
Copy Markdown
Member

@mister-roboto

Copy link
Copy Markdown

@gforcada thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@gforcada gforcada changed the title feat: move metadata from setup.py to pyproject.toml. Move metadata from setup.py to pyproject.toml Aug 15, 2026
@gforcada
gforcada force-pushed the convert-setup-py-to-pyproject-toml branch from a75d8f3 to 3409349 Compare September 8, 2026 13:00
@gforcada
gforcada merged commit 0120d1c into master Sep 8, 2026
10 of 14 checks passed
@gforcada
gforcada deleted the convert-setup-py-to-pyproject-toml branch September 8, 2026 13:02
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.

2 participants