How to upgrade Plone in kitconcept.core#
This document describes how to upgrade Plone in kitconcept.core.
Note
This process assumes that you have installed uvx in your machine.
If you haven't, please follow the instructions in the uvx documentation.
Use the
repoplonecommand, replace the version with the desired one:
$ uvx repoplone deps upgrade backend 6.1.4
Update the tests that check the Plone version in the backend. Make a quick search for
plone_versionin thebackend/testsfolder and update the version accordingly (at the time of the writing:backend/tests/services/system/test_system_get.pyandbackend/tests/tools/test_migration_tool.py).Create an upgrade step. Add an upgrade step for the
kitconcept.core:baseprofile. First, check what changes were made inProducts.CMFPlone, and evaluate if we need to backport these changes to our profile:If a new registry configuration is created
Changes to default types or permissions We at least need a null upgrade step, so that the migration tool has a chance to upgrade dependencies.
<configure xmlns="http://namespaces.zope.org/zope" xmlns:genericsetup="http://namespaces.zope.org/genericsetup" > <genericsetup:upgradeSteps profile="kitconcept.core:base" source="20251209001" destination="20260122001" > <!-- This step upgrade all dependencies of kitconcept.core --> <genericsetup:upgradeStep title="Upgrade dependencies for Plone 6.1.4" handler="..utils.null_upgrade_step" /> <!-- Additional step updating registry settings defined in kitconcept.core:dependencies --> <genericsetup:upgradeDepends title="Adds disable_profile_links setting to kitconcept settings" import_profile="kitconcept.core:dependencies" import_steps="plone.app.registry" /> </genericsetup:upgradeSteps> </configure>