# Update Xperience

> Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh.

- Skill: `kentico/update-xperience` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add kentico/update-xperience`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kentico/update-xperience/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Kentico (https://skillmd.com/u/kentico)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kentico/update-xperience

---


You are tasked with updating an Xperience by Kentico project to a newer version. The official release notes and update documentation are the source of truth — follow them, do not invent update steps.

## Workflow

### 1. Determine the versions

- Identify the current version from the `Kentico.Xperience.*` NuGet package references in the project.
- Identify the target version: use the version passed as an argument if provided, otherwise the latest available.

### 2. Review the release notes

- Read the release notes in the [Changelog](https://docs.kentico.com/changelog) for **every version between the current and target version**.
- Note breaking changes, deprecations, new object types for CI/CD, and any manual steps.
- **Follow the pages linked from the release notes** that guide through specific feature updates — they contain the instructions for adapting the project.

### 3. Follow the official update procedure

- Read `references/update-docs.md` and fetch the relevant documentation pages.
- Perform the update as documented — do not substitute your own procedure or external tools; everything needed (including CI handling) is built into the product's CLI.

### 4. Resolve breaking changes and obsolete API

- Apply the code and configuration changes required by the release notes and their linked guides.
- Build the solution and fix remaining errors caused by the update.
- After the build succeeds, resolve obsolete-API warnings: migrate the affected code to the replacements described in the obsolete warning messages.

### 5. Update CI/CD repository configuration

- If the project uses the `IncludedObjectTypes` element in a CI or CD `repository.config`, collect the **New object types for CI/CD** entries from the release notes of every version in the update path.
- Add the new object types the project should include to the allowlist, per the official update documentation.

### 6. Verify and report

- Verify the result (build, tests if present).
- Summarize what was updated and which release-note items required action.