This action runs composer outdated on your project and generates a markdown table with the results. This is handy for adding to a pull request output.
In your workflow, define a step which refers to the action:
steps:
# ...
- name: Composer Outdated
id: composer_outdated
uses: edwilde/composer-outdated-action@2
with:
extra-arguments: '--direct'This is an example of the output for the outdated table, including the abandoned packages.
| Package | Current | New | Compare | Details |
|---|---|---|---|---|
| v2.2.1 | v2.2.1 | Compare | Save locations using lati… | |
| bramus/monolog-colored-line-formatter | 2.0.3 | 3.1.2 | Compare | Colored Line Formatter fo… |
| doctrine/lexer | 2.1.0 | 3.0.1 | Compare | PHP Doctrine Lexer parser… |
| silverstripe/framework | 4.13.39 | 5.1.15 | Compare | The SilverStripe framewor… |
Extra arguments can be passed to the composer outdated command using the extra-arguments parameter. These should be separated with a space, in the same way as you would add them on the command-line.
This is the markdown table displaying all outdated packages, their current version and the latest version.
In this output, any packages which are not outdated (i.e. use the symbol = in the raw output) are removed.
This can be output in later steps using:
${{ steps.composer_outdated.outputs.composer_outdated }}
The raw exit code from the composer outdated command, useful for debugging.
This can be output in later steps using:
${{ steps.composer_outdated.outputs.composer_outdated_exit_code }}
Cannot use silverstripe/framework 4.13.39 as it requires ext-intl * which is missing from your platform.
Make sure the PHP extension is defined in composer.json
"config": {
"platform": {
"php": "8.1.2",
"ext-intl": "1.1.0"
},
}