Skip to content

bringyourownideas/silverstripe-composer-update-checker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

bf09846 · Jun 19, 2024
May 17, 2024
Mar 9, 2023
Jun 5, 2018
May 7, 2024
Jun 5, 2024
Apr 29, 2022
Dec 13, 2015
Jun 8, 2018
Apr 12, 2016
Aug 23, 2015
Apr 19, 2023
Apr 28, 2014
Feb 2, 2024
Nov 10, 2021
Feb 2, 2024
Aug 2, 2022

Repository files navigation

Silverstripe Composer update checker

CI Silverstripe supported module

Checks if any of your Composer dependencies needs to be updated, and tracks the available and latest versions that can be updated to.

This module only runs the actual checks and saves the information into fields on the Package DataObject. The fields are also added to the report that the Silverstripe Maintenance module provides.

The bulk of the heavy lifting here is done using the Composer PHP API, which mimics the behaviour of using Composer on the command line to install or update PHP packages.

Installation

composer require bringyourownideas/silverstripe-composer-update-checker

Note for private repositories

Please note that if your project has modules that are stored in private repositories, the server running the BuildTask will need to have the necessary permissions to access the private VCS repositories in order for the report to include update information about necessary updates to the module.

If the process looking for available updates fails (for example, due to an authentication failure against a private repository) the process will fail gracefully and allow the rest of the report generation to continue.

Users on the Common Web Platform will currently not be able to retrieve information about updates to private repositories.

Documentation

Please see the user guide section of the Silverstripe Maintenance module.

Terminology

The "Available" version will show the latest available version for a Package that can be installed, given the package's semver constraint. If the version is the same as that which is already installed, the column will be empty in the report.

The "Latest" version is the latest available version regardless of the package's semver constraint.

When tracking available and latest versions, the current, available and latest version hashes are also stored against the Package. This is to help with showing whether updates are available within a branch alias (for example: 1.x-dev).

Contributing

Please see the contributing guide.