Remove composer lockfiles #562
Merged
Conversation
This file contains hidden or 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
pkevan
approved these changes
Jun 4, 2025
ryelle
added a commit
to WordPress/wporg-repo-tools
that referenced
this pull request
Jun 6, 2025
See WordPress/wporg-main-2022#562, composer.lock was removed which causes this command to return an error, halting the rest of the action.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See https://wordpress.slack.com/archives/C02QB8GMM/p1746982331966409
The lock files are going to be outdated most of the time and the suggested path is to run
composer updateafter cloning the repo. In such a case, the lock files do not serve a purpose.Remove and ignore them.
Props kraftbj, kimjiwoon
Screenshots
How to test the changes in this Pull Request: