Download the PHP package webworkerjoshua/composer-check-updates without Composer

On this page you can find all versions of the php package webworkerjoshua/composer-check-updates. 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?

Example code of webworkerjoshua/composer-check-updates

Informations about the package composer-check-updates

composer-check-updates

CI

Interactive dependency update checker for Composer, inspired by npm-check-updates.

composer outdated tells you what's newer. composer update only moves you within your version ranges. This plugin shows both kinds of updates at once — those satisfying your composer.json constraints and those beyond them (new minors/majors) — lets you pick updates with the arrow keys and Space, rewrites composer.json where needed, and runs composer update for exactly what you selected.

Installation

Composer will ask you to trust the plugin (allow-plugins); confirm with yes.

Global installation

Install once, use in every project:

Globally installed Composer plugins are loaded for every composer invocation, so composer check-updates / composer ccu then works in any project directory. The global install also provides a bare ccu command — make sure Composer's global bin directory is on your PATH (find it with composer global config bin-dir --absolute, typically ~/.composer/vendor/bin on macOS):

Usage

Packages with updates both inside and outside the range

A package like monolog/monolog with constraint ^1.0, installed at 1.25.0, has two distinct upgrade paths: 1.27.1 (in range) and 3.10.0 (major). It therefore appears twice — once in In range and once in Major — and each entry cross-references the other (or 3.10.0, see Major). The two entries are mutually exclusive: selecting one automatically deselects the other, so you always make exactly one decision per package. a (select all) prefers the in-range entry — majors stay opt-in.

Below 1.0.0, a minor bump (0.1.0 → 0.2.0) is shown as Major: semver makes no compatibility promise for 0.x, and Composer's ^0.1.0 does not allow 0.2.0 either. Patch bumps within the same 0.x minor stay patches.

Filtering

Patterns support * wildcards and match case-insensitively; rejects win over filters.

Non-interactive usage

When stdout is not a TTY (CI, pipes) the command prints the grouped listing instead of starting the picker.

How it works

The plugin uses Composer's own resolver APIs (RepositorySet + VersionSelector), so it sees exactly the packages your project sees: custom repositories, minimum-stability, stability flags, and platform requirements (your PHP version and extensions) are all respected. For each root requirement it asks for the best candidate within your constraint and the best candidate overall; composer.json edits go through Composer's JsonManipulator, which preserves your file's formatting.

Requirements

Development

License

MIT

All versions of composer-check-updates with dependencies

PHP Build Version
Package Version
Requires php Version >=8.3
composer-plugin-api Version ^2.3
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 webworkerjoshua/composer-check-updates contains the following files

Loading the files please wait ...