Skip to main navigation Skip to main content Skip to page footer
Wolfgang Wagner - TYPO3 Seminare, Workshops, Tutorials, Support
TYPO3 13.4.28 and 12.4.45: Maintenance releases with important phase change

TYPO3 13.4.28 and 12.4.45: Maintenance releases with important phase change

Have the article read aloud.

Loading the Elevenlabs Text to Speech AudioNative Player...
| Estimated reading time : min.
This article was automatically translated using DeepL. Therefore, inaccuracies may occur.

TYPO3 v12 gets its last public update. What this means for current projects and what bug fixes are in v13.4.28.

On April 14, 2026, the TYPO3 Core Team released two new maintenance releases: TYPO3 13.4.28 LTS and TYPO3 12.4.45 LTS. Both versions contain only bug fixes and maintenance work. There are no security-related changes.

The update is uncomplicated: No database updates necessary, just clear the cache.

But the real news is elsewhere.

TYPO3 v12 goes into retirement

TYPO3 v12.4.45 is expected to be the last public release of TYPO3 v12. On April 30, 2026, the v12 branch will switch to the ELTS phase (Extended Long-Term Support). From this date, updates for v12 will only be available as a paid service.

Anyone still running projects on v12 should now have a concrete plan for switching to v13 or v14. Or even consider ELTS.

At the same time, TYPO3 v13 is moving into the "Priority Bugfixes" phase. This means that from now on, only security fixes and compatibility updates will be available for v13. New features will only be released in v14.

Selected bugfixes in TYPO3 13.4.28

Even though it is a pure maintenance release, there are a few fixes worth mentioning:

  • New index for content_from_pid in the pages table: this can improve performance on larger installations.
  • Workspace preview handling improved: The preview handling is now derived cleanly from the event context.
  • Site::isTypoScriptRoot() in the BackendConfigurationManager: Is now taken into account, which is relevant in multi-site setups.
  • Missing JS module in RecordLinkHandler added: An error that could occur when linking records in the backend.
  • Pages with non-existent language: No more error if a page is called with a non-configured language.
  • ENV variables in the Site Configuration: Environment variables in the Site Configuration are now persisted correctly.
  • Fluid Standalone updated to 4.6.0
  • Update to NodeJS 24 LTS and TypeScript v6

TYPO3 12.4.45: Few changes, lots of symbolism

As expected, the latest public v12 release is lean. The changes are limited to tooling updates (PHPStan, NodeJS 24 LTS), a performance improvement in the PolymorphicDeserializer and the fixing of vulnerable npm dev dependencies.

Nothing dramatic in terms of content. But symbolically a milestone: After more than three years of public support, TYPO3 v12 is going into well-deserved retirement.

What you should do now

  1. Install updates: As with every maintenance release: update promptly. Composer users know the game.
  2. Check v12 projects: As of April 30, there will be no more free updates for v12. If you are still using v12, you should plan your upgrade path now.
  3. Keep an eye on v14: Active development is now fully focused on v14. If you want to stay up to date, you should familiarize yourself with the new concepts.
Back

Related Links

Do you have a question or want to discuss the topic?

In the Community Hub for TYPO3 you can exchange ideas with other TYPO3 users. And if you don't want to miss any new articles: The TYPO3 Newsletter comes once a month, without spam.

[Translate to English:] Wolfgang Wagner, TYPO3 Experte und Trainer

Hi, I'm Wolfgang.

I have been working with TYPO3 since 2006. Not in theory, but in real projects with real deadlines. I've probably had the problems you're having three times already.

At some point, I started putting my knowledge into video courses. Not because I like being in front of the camera, but because I kept hearing the same questions over and over again. There are now hundreds of videos. Every single one was the result of a specific question from a specific project.

What makes me different from a YouTube tutorial: I not only know the solution, but also the context. Why something works. When it doesn't work. And which mistakes you can avoid because I've already made them.

My participants use me as a sparring partner. Not in the sense of "call me anytime", but like this: You come to the live session with a specific problem, post your question in the community or watch the appropriate video. And get an answer that works because it comes from practical experience.

As a member of the TYPO3 Education & Certification Committee, I make sure that the certification exams are kept up to date. What is tested there flows directly into my courses.