textpattern / lock
Lock your Textpattern CMS version or define package dependencies
- dev-master / 4.x-dev
- 4.8.8
- 4.8.7
- 4.8.6
- 4.8.5
- 4.8.4
- 4.8.3
- 4.8.2
- 4.8.1
- 4.8.0
- 4.7.3
- 4.7.2
- 4.7.1
- 4.7.0
- 4.6.x-dev
- 4.6.2
- 4.6.1
- 4.6.0
- 4.6.0-beta.3
- 4.6.0-beta.2
- 4.6.0-beta
- 4.5.x-dev
- 4.5.7
- 4.5.5
- 4.5.4
- 4.5.3
- 4.5.2
- 4.5.1
- 4.5.0
- 4.4.1
- 4.4.0
- 4.3.0
- 4.2.0
- 4.0.8
- 4.0.7
- 4.0.6
- 4.0.5
- 4.0.4
- 4.0.3
- 4.0.2
- 4.0.1
- 4.0.0
- 1.0.0-rc.5
- 1.0.0-rc.4
- 1.0.0-rc.1
This package is auto-updated.
Last update: 2024-11-19 02:54:27 UTC
README
Composer meta package for Textpattern CMS. This package can be used to lock the installed Textpattern version and handle Textpattern version dependencies in packages. This package makes sure your Textpattern installation and packages are compatible and can work together, making the painless dependency management reality.
Locking your Textpattern installation version
When you start using Composer to manage Textpattern packages, plugins and themes, you should lock in your Textpattern version. This makes sure the packages you install are compatible with the Textpattern version you have. You can lock in your Textpattern version using Composer's require command.
$ composer require textpattern/lock:4.7.3
Where the 4.7.3
is the Textpattern version you have.
Defining required Textpattern version as a dependency in your packages
Textpattern plugin and theme developers can define the compatible and required Textpattern versions using the textpattern/lock package. You can set requirements using the require property, or exclude versions using the conflict. In your package's composer.json
:
{ "require": { "textpattern/lock": ">=4.5.0" } }
The above would require Textpattern version 4.5.0 or newer, and the plugin or theme will not be installed if the user's Textpattern installation doesn't meet the requirements. See Composer schema and basic usage for more information about defining requirements.