Download the PHP package b13/typo3-updater without Composer

On this page you can find all versions of the php package b13/typo3-updater. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package typo3-updater

b13/typo3-updater - A Composer plugin to help you update TYPO3 core and extensions

Upgrading a TYPO3 project to a new major version involves several manual steps:

This plugin automates that entire workflow into two commands and a clear three-step process.

Installation

You can set it up for all your projects in a global way:

Upgrade workflow

Upgrading from e.g. TYPO3 12 to 13 is a three-step process:

Step 1: Prepare extensions for the target TYPO3 version

Updates extensions to versions that are compatible with the target TYPO3 version, while still running on the current core. This is the safest first step because it doesn't touch the core yet — only extensions are updated.

The command shows a compatibility table comparing each extension against both the current and target TYPO3 versions, then interactively offers to bump constraints and run composer require.

Use --dry-run to only see the table without making changes.

Step 2: Update TYPO3 core (and remaining extensions)

Updates all typo3/cms-* constraints to the target version. It also detects any remaining extensions that are still incompatible and finds their latest compatible versions — so everything is resolved in one composer update -W call.

Use --dry-run to preview all changes without modifying anything.

Step 3: Update extensions to their latest versions

Now that the core is at 13.4, running the same command again finds the latest available version of each extension for the running TYPO3 version. This ensures you're not stuck on the minimum compatible version but running the newest release.

Use --dry-run to audit which extensions have newer versions available.

Quick reference

Commands

composer typo3:core:update <version> - Update TYPO3 core and extensions

The main command for upgrading the TYPO3 core. It handles core packages and third-party extensions in one go.

What it does under the hood:

  1. Reads the root composer.json and collects all typo3/cms-* packages whose constraints don't yet match the target version
  2. Scans all installed extensions (packages of type typo3-cms-extension) and checks whether their typo3/cms-core constraint is compatible with the target version
  3. For each incompatible extension, queries Packagist for the latest compatible version (stable first, falls back to pre-release if no stable version exists)
  4. Displays up to three tables:
    • Core packages: typo3/cms-* constraint changes (e.g. ^12.4 -> ^13.4)
    • Extensions to upgrade: extensions that need a version bump, including the new constraint (pre-release versions are flagged)
    • Unresolvable extensions: extensions with no published version compatible with the target (warning)
  5. Shows the exact composer update ... -W command that will be executed
  6. On confirmation: writes all new constraints to composer.json (respecting require vs require-dev) and runs composer update with -W (update with all dependencies)
  7. On failure: reverts composer.json to its original state

Without this plugin you would need to manually: open composer.json, change every typo3/cms-* constraint, search Packagist or TER for each extension to find a compatible version, update those constraints too, run composer update, and if it fails, figure out which package is the problem and revert your changes.

composer typo3:extensions:update <version> - Check and update extension compatibility

A versatile command for managing extensions. It serves two purposes depending on the context:

What it does under the hood:

  1. Loads all installed TYPO3 extensions (from require, require-dev, and path repositories)
  2. For each extension, queries Packagist for the latest version compatible with the currently installed TYPO3 core
  3. When the target version is newer than the installed version (upgrade scenario), additionally:
    • Queries Packagist for the latest version compatible with the target TYPO3 version
    • Shows a compatibility column comparing current vs target
  4. Displays a compatibility table with columns:
    • Current installed version
    • Latest compatible version (for the current core)
    • Compatibility status for the current TYPO3 version
    • Target TYPO3 compatibility (only in upgrade scenario)
  5. With --dry-run: stops after the table
  6. Without --dry-run: asks for confirmation, then interactively offers to:
    • Bump version constraints in local package composer.json files (e.g. path repository extensions)
    • Run composer require (and composer require --dev separately for dev dependencies) to update extensions
  7. On failure: reverts all modified composer.json files to their original state

Without this plugin you would need to: manually check each extension's page on Packagist or TER, compare version constraints, figure out which version supports your target TYPO3 version, and update constraints in potentially multiple composer.json files across your project.

Credits

This extension was created by Jochen Roth in 2023 for b13 GmbH, Stuttgart.

Find more TYPO3 extensions we have developed that help us deliver value in client projects. As part of the way we work, we focus on testing and best practices to ensure long-term performance, reliability, and results in all our code.

All versions of typo3-updater with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer/composer Version ^2.0
composer-plugin-api Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package b13/typo3-updater contains the following files

Loading the files please wait ...