E51C build: Fix composer.lock not up to date by theofidry · Pull Request #1379 · phpbrew/phpbrew · GitHub
[go: up one dir, main page]

Skip to content

build: Fix composer.lock not up to date#1379

Open
theofidry wants to merge 1 commit intophpbrew:masterfrom
theofidry:build/fix-composer-lock
Open

build: Fix composer.lock not up to date#1379
theofidry wants to merge 1 commit intophpbrew:masterfrom
theofidry:build/fix-composer-lock

Conversation

@theofidry
Copy link
Contributor

Extracted from #1375.

Currently:

$ composer validate
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
- The lock file is not up to date with the latest changes in composer.json, it is recommended that you run `composer update` or `composer update <package name>`.
- The package "corneltek/cliframework" is pointing to a commit-ref, this is bad practice and can cause unforeseen issues.
- require.corneltek/cliframework : exact version constraints (3.0.x-dev#0e69e4d9d8ee6c8b5abb7ebf0cf846e47d93b656) should be avoided if the package follows semantic versioning

The two warnings cannot be fixed, but they only make composer validate fail if the --strict option is passed.

I fixed this by running composer update --lock.

Currently:

```shell
$ composer validate
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
- The lock file is not up to date with the latest changes in composer.json, it is recommended that you run `composer update` or `composer update <package name>`.
- The package "corneltek/cliframework" is pointing to a commit-ref, this is bad practice and can cause unforeseen issues.
- require.corneltek/cliframework : exact version constraints (3.0.x-dev#0e69e4d9d8ee6c8b5abb7ebf0cf846e47d93b656) should be avoided if the package follows semantic versioning
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments

0