Plone 6.0.14 and 6.1.0b2 are out with Python 3.13 support.

[mauritsvanrees]

Marked as draft PR, because the plone-backend Docker images are not ready yet.

---

📚 Documentation preview 📚: https://plone6--1823.org.readthedocs.build/

[stevepiercy]

Preview changes:

• https://plone6--1823.org.readthedocs.build/backend/upgrading/intro.html#in-place-migrations
• https://plone6--1823.org.readthedocs.build/conceptual-guides/package-management.html#manage-backend-python-packages
• https://plone6--1823.org.readthedocs.build/install/create-project-cookieplone.html#python
• https://plone6--1823.org.readthedocs.build/admin-guide/install-buildout.html#python
• https://plone6--1823.org.readthedocs.build/admin-guide/install-pip.html#python
• https://plone6--1823.org.readthedocs.build/install/create-project.html#python

[mauritsvanrees]

I saw one place where we were already using PLONE_BACKEND_PATCH_VERSION and we actually should not:

https://plone6--1823.org.readthedocs.build/conceptual-guides/package-management.html#manage-backend-python-packages

It has this example of an unresolvable version conflict:

# constraints.txt with unresolvable version conflict
-c https://dist.plone.org/release/6.0.14/constraints.txt
plone.api>=2.0.0a3

But that is actually not a conflict! The plone.api version in the 6.0.14 constraints (and actually already in 6.0.0) is higher than 2.0.0a3, so there is no conflict.

I have pushed a commit to use different versions, which are fine to be hardcoded:

-c https://dist.plone.org/release/6.0.9/constraints.txt
plone.api>=2.1.0

Ah, the preview has just updated.

[mauritsvanrees]

I will mark this as ready for review/merge now, as the Docker images are ready.

[stevepiercy]

Will merge when green.