Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Composer packages and Packagist

Publish an extension as a Composer package - the package name and type, version constraints, tags, Packagist and its webhook, installing a package into an installation, and updating safely.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/creators/app-creators/composer-and-packagist.md

On this page

Composer packages and Packagist

This page is for application creators who publish their extension so installations can composer require it. Exponential and every extension it ships are Composer packages on Packagist.

Contents

  1. Package basics
  2. Versions and constraints
  3. Publishing on Packagist
  4. Installing into an installation
  5. Updating safely

Package basics

KeyValue
namevendor/name in lower case
typeezpublish-legacy-extension
extra.ezpublish-legacy-extension-namethe directory name under extension/
licensean SPDX id, for example GPL-2.0-or-later
requirePHP version and libraries

Versions and constraints

  • Versions come from Git tags (v1.2.3). A published tag is permanent: never move or delete it; publish the next version instead (Versions and releases).
  • ~1.2.3 means >=1.2.3 <1.3.0: the last position given floats. This is how the root composer.json pins extensions ("se7enxweb/eztags": "~2.4.11").

Publishing on Packagist

  1. Push the repository to a public host (the se7enxweb extensions are on GitHub).
  2. Submit the repository URL on Packagist.
  3. Add Packagist's webhook to the repository, so new tags appear without a manual update; a package that stays on an old version on Packagist usually has no webhook.
  4. Tag a release; check that Packagist shows it.

Installing into an installation

composer require yourvendor/expdemo:~1.0.0
php bin/php/ezpgenerateautoloads.php -e

Then activate it (3.5 Extensions are Composer packages).

Updating safely

  • Update one package deliberately (composer update yourvendor/expdemo), after reading its release notes; not composer update on everything on a live site.
  • A hand-made git clone in place of a package Composer installed as an archive is replaced by the next update, history included; let Composer make clones (preferred-install) if you develop in place.
  • Test the update on staging first (A deployment pipeline).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x