Download the PHP package disrex/magento-patch-installer without Composer

On this page you can find all versions of the php package disrex/magento-patch-installer. 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 magento-patch-installer

disrex/magento-patch-installer

A Composer plugin that applies patches to Magento 2 and Adobe Commerce, checks on every Composer run that they are still on disk, and fails the run when one is missing. It was built for Adobe's monthly isolated security patches, which a store only receives by applying the files itself.

Full documentation: https://disrex-group.github.io/magento-patch-installer/

Install

You only require the patch package; this installer comes with it as a dependency. The allow-plugins line names the installer because it is the plugin Composer has to trust. Without that line a CI run skips the plugin without a word and exits 0 on an unpatched store. Without trust the run fails and names the package.

Use

A patch package can mark a patch optional. It stays off until the project enables it under extra.magento-patches.sources with a reason; see Declaring patches.

Exit codes: 0 all in place, 1 missing, 2 conflict, 3 configuration error. Run verify as its own pipeline step after composer install.

What it guarantees

Requirements

Magento 2.4.4 or later or Mage-OS 1.0 or later, PHP 7.4 to 8.5, Composer 2.2 or later, and git on the PATH. CI runs the end-to-end check on Magento 2.4.6-p15 to 2.4.9 and Mage-OS 1.3.1, 2.3.0 and 3.6.0.

Development

Releases use git-cliff with conventional commits:

The tag triggers the GitHub release, and Packagist picks it up through its webhook.

License

MIT, see SECURITY.md.

All versions of magento-patch-installer with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
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 disrex/magento-patch-installer contains the following files

Loading the files please wait ...