[GH-ISSUE #1596] Property "Lock" in composer.json #679

Closed
opened 2026-03-04 02:16:56 +03:00 by kerem · 0 comments
Owner

Originally created by @digitall-it on GitHub (Sep 21, 2021).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1596

Monolog version 1

While validating via PHPStorm the composer.json of my own code to be published on Packagist, it has descended to requirements as casually I didn't check out that box, and it is complaining about monolog

composer validate --no-interaction --ansi --verbose --no-check-all --with-dependencies

monolog/monolog is valid for simple usage with Composer but has
 strict errors that make it unable to be published as a package
 # Publish errors
 - The property lock is not defined and the definition does not allow additional properties

monolog/monolog's "lock": false last row seems to be the culprit. I didn't find that property on the composer documentation.

Originally created by @digitall-it on GitHub (Sep 21, 2021). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1596 **Monolog version 1** While validating via PHPStorm the composer.json of my own code to be published on Packagist, it has descended to requirements as casually I didn't check out that box, and it is complaining about monolog `composer validate --no-interaction --ansi --verbose --no-check-all --with-dependencies` ``` monolog/monolog is valid for simple usage with Composer but has  strict errors that make it unable to be published as a package  # Publish errors  - The property lock is not defined and the definition does not allow additional properties ``` monolog/monolog's `"lock": false` last row seems to be the culprit. I didn't find that property on the composer documentation.
kerem 2026-03-04 02:16:56 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#679
No description provided.