typo3-extension-upgrade

Category: Development & Coding | Uploader: netresearch | Downloads: 0 | Version: v1.0（Latest）

Use when upgrading TYPO3 extensions to newer LTS versions (v11->v12, v12->v13, v13->v14), running Extension Scanner, Rector, Fractor, PHPStan, fixing deprecated APIs, or resolving compatibility issues. Also triggers on: migration, version upgrade, deprecated API, dual-version compatibility.

Changelog: Source: GitHub https://github.com/netresearch/typo3-extension-upgrade-skill

Directory Structure

Current level: tree/main/skills/typo3-extension-upgrade/

📁 assets/
- 📄 .php-cs-fixer.php 6.0 KB
- 📄 fractor.php 1017 B
- 📄 phpstan.neon 734 B
- 📄 phpunit.xml 1.3 KB
- 📄 rector.php 2.0 KB
📁 references/
- 📄 api-changes.md 30.0 KB
- 📄 dual-compatibility.md 2.4 KB
- 📄 pre-upgrade.md 3.8 KB
- 📄 real-world-patterns.md 4.7 KB
- 📄 third-party-dependency-upgrades.md 8.2 KB
- 📄 toolchain-output.md 943 B
- 📄 troubleshooting.md 4.9 KB
- 📄 upgrade-v11-to-v12.md 1.5 KB
- 📄 upgrade-v12-to-v13.md 813 B
- 📄 upgrade-v13-to-v14.md 2.0 KB
- 📄 verification.md 1.9 KB
📄 checkpoints.yaml 19.6 KB
📄 SKILL.md 3.9 KB

SKILL.md

---
name: typo3-extension-upgrade
description: "Use when upgrading TYPO3 extensions to newer LTS versions (v11->v12, v12->v13, v13->v14), running Extension Scanner, Rector, Fractor, PHPStan, fixing deprecated APIs, or resolving compatibility issues. Also triggers on: migration, version upgrade, deprecated API, dual-version compatibility."
---

# TYPO3 Extension Upgrade Skill

Systematic framework for upgrading TYPO3 extensions to newer LTS versions.
Extension code only -- NOT for project/core upgrades.

## Upgrade Toolkit

| Tool | Purpose | Files |
|------|---------|-------|
| Extension Scanner | Diagnose deprecated APIs | TYPO3 Backend |
| Rector | Automated PHP migrations | `.php` |
| Fractor | Non-PHP migrations | FlexForms, TypoScript, YAML, Fluid |
| PHPStan | Static analysis | `.php` |

## Core Workflow

1. Complete planning phase (consult `references/pre-upgrade.md`)
2. Create feature branch (verify git is clean)
3. Update `composer.json` constraints for target version
4. **Audit third-party dependencies** for major version changes (consult `references/third-party-dependency-upgrades.md`)
5. Run `rector process --dry-run` then review and apply
6. Run `fractor process --dry-run` then review and apply
7. Run `php-cs-fixer fix`
8. Run `phpstan analyse` **against each supported dependency version** and fix errors
9. Run `phpunit` and fix tests
10. Test in target TYPO3 version(s)
11. Verify success criteria (consult `references/verification.md`)

## When NOT to Apply Automatically

Do NOT blindly apply Rector/Fractor if dual-version compatibility is needed,
tests are missing, changes are unclear, or complex APIs (DBAL, Extbase) are
affected. Instead: apply specific rules manually, test between each change.

## Third-Party Dependency Upgrades

When `composer.json` widens constraints to a new major version of ANY dependency:

1. **Enumerate** all usages of the dependency's API in the codebase
2. **Cross-reference** against the new version's API (removed/renamed methods)
3. **Flag** methods called on interfaces that only exist on concrete classes
4. **Verify** test mocks reference methods existing in ALL supported versions
5. **Use adapter pattern** when method signatures differ between versions
6. **Run PHPStan** against EACH supported major version

See `references/third-party-dependency-upgrades.md` for details.

## Quick Commands

```bash
rector process --dry-run && rector process        # PHP migrations
fractor process --dry-run && fractor process       # Non-PHP migrations
php-cs-fixer fix && phpstan analyse && phpunit     # Quality checks
```

## Asset Templates

Config templates in `assets/`: `rector.php`, `fractor.php`, `phpstan.neon`, `phpunit.xml`, `.php-cs-fixer.php`

## References

| Reference | Use when... |
|-----------|-------------|
| `references/pre-upgrade.md` | Starting an upgrade: planning checklist, version audit, risk assessment |
| `references/api-changes.md` | Checking deprecated/removed APIs by TYPO3 version |
| `references/upgrade-v11-to-v12.md` | Upgrading from TYPO3 v11 to v12 |
| `references/upgrade-v12-to-v13.md` | Upgrading from TYPO3 v12 to v13 |
| `references/upgrade-v13-to-v14.md` | Upgrading from TYPO3 v13 to v14 |
| `references/dual-compatibility.md` | Maintaining dual compatibility (v12 + v13) |
| `references/real-world-patterns.md` | Looking for real-world migration examples |
| `references/toolchain-output.md` | Understanding Rector/Fractor dry-run output |
| `references/troubleshooting.md` | Rector broke code, PHPStan errors, test failures |
| `references/third-party-dependency-upgrades.md` | Upgrading non-TYPO3 dependencies (major version bumps, adapter patterns) |
| `references/verification.md` | Checking success criteria and real-world testing |

## External Resources

- [TYPO3 Rector](https://github.com/sabbelasichon/typo3-rector)
- [Fractor](https://github.com/andreaswolf/fractor)
- [TYPO3 Core Changelog](https://docs.typo3.org/c/typo3/cms-core/main/en-us/)

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

typo3-extension-upgrade

Directory Structure

SKILL.md

Report

Notice