cd-repository-upgrade

Name: cd-repository-upgrade
Availability: InStock
Author: Kentico

Migrate Kentico CD Repository repository.config from v1 to v2 syntax.

14|7|Updated Nov 25, 2025

Search Tags:#ci-cd #configuration upgrade #xml migration #kentico #cd repository #repository.config #content item filters

Ready to run

npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill cd-repository-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cd-repository-upgrade
Source: https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/configure-cd-repository/skills/cd-repository-upgrade
Command: npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill cd-repository-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of having an outdated CD Repository repository.config (v1 syntax) that blocks required v2 features like advanced content item filtering and improved restore performance.

Core Features & Use Cases

Config migration with safeguards: Validates XML, detects whether the configuration is already v2, and creates a backup before overwriting.
Required v1→v2 transformations: Adds Version="2", ensures IncludedObjectTypes is explicit, and migrates content item code name filters from ObjectFilters into ContentItemFilters.
Context-aware discovery: If you don’t provide a path, it searches for cd-repository-context.json and uses cdRepositoryConfigPath to locate the correct config file, then updates the context version to prevent re-discovery.

Quick Start

Ask the skill to migrate your CD repository configuration by running: migrate using cd-repository-upgrade with the argument cd-repository-upgrade "(path to repository.config)".

Frequently Asked Questions about cd-repository-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a Kentico CD repository.config from v1 to v2 syntax?▼

To migrate a Kentico CD repository.config from v1 to v2, the process validates the XML, creates a v1 backup, sets Version="2", enforces explicit IncludedObjectTypes, and migrates cms.contentitem filters into ContentItemFilters.

What is the purpose of upgrading a cd repository.config to v2?▼

Upgrading a cd repository.config to v2 enables advanced content item filtering for cms.* object types and faster restore workflows during CI/CD configuration maintenance.

Does the repository.config migration automatically find my configuration file?▼

If no path is provided, the migration searches for cd-repository-context.json, uses the cdRepositoryConfigPath value to locate the config file, and updates the context version to prevent re-discovery.

Can I safely convert content item filters in my deployment configuration without losing data?▼

You can safely convert content item filters because the process validates the XML, detects if the configuration is already v2, and creates a backup before overwriting your deployment store configuration.

When do I need to update IncludedObjectTypes during XML migration?▼

You must update IncludedObjectTypes during XML migration when upgrading to v2, because the process enforces explicit IncludedObjectTypes definitions to support the new content item filter requirements.