php strategy should upgrade composer.lock hash if present #2274
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Hello!
When releasing a tag using release-please in a php project, the
content-hash
part of thecomposer.lock
file is kept unchanged. This triggers warnings in composer due to thecomposer.json
file may not be synced with thecomposer.lock
.This is a kink of composer, due to the fact that no other dependency manager that I know of does this (release please works like a breeze in nodejs projects).
I've looked up in the code and the only reasonable way to do this is adding an
Update
in thesrc/strategies/php.ts
. But this cannot be done due to the fact that I need to change thecomposer.lock
based off the now updatedcomposer.json
file, and theUpdate
interface does not support multiple paths where to load the file from.Any suggestions on how to implement this?
The text was updated successfully, but these errors were encountered: