Updated composer lock file after running composer normalize #232
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sometimes the normalize changes the part composer hashes for the lockfile hash and results in failures on the CI which expect the lockfile to be update to date with composer.json. By updating the lockfile after running normalize that doesn't happen anymore.
boring-cyborg
bot
added
Dependencies 📦
WyriHaximus
deleted the
updated-composer-lock-file-after-running-composer-normalize
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes the normalize changes the part composer hashes for the lockfile hash and results in failures on the CI which expect the lockfile to be update to date with composer.json. By updating the lockfile after running normalize that doesn't happen anymore.