Explicit the version where script-aliases was included (#11847)
Since this was included in a minor version, it's nice to tell the user if this feature is available on the version they're running or if they need to upgrade. If it's not available, the only hint (besides the missing aliases on `composer list`) is the mild complaint at `composer validate`.pull/11866/head
parent
8c61f812a4
commit
596a384c97
|
@ -425,7 +425,7 @@ To set an environment variable in a cross-platform way, you can use `@putenv`:
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
## Custom descriptions.
|
## Custom descriptions
|
||||||
|
|
||||||
You can set custom script descriptions with the following in your `composer.json`:
|
You can set custom script descriptions with the following in your `composer.json`:
|
||||||
|
|
||||||
|
@ -442,9 +442,9 @@ describe what the scripts do when the command is run.
|
||||||
|
|
||||||
> **Note:** You can only set custom descriptions of custom commands.
|
> **Note:** You can only set custom descriptions of custom commands.
|
||||||
|
|
||||||
## Custom aliases.
|
## Custom aliases
|
||||||
|
|
||||||
You can set custom script aliases with the following in your `composer.json`:
|
As of Composer 2.7, you can set custom script aliases with the following in your `composer.json`:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in New Issue