chore: Include composer lock in repository #49
Merged
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
Prevent composer installations to install potentially unsuported package versions. (Yeah, sometimes there are unexpected breaking changes in either minor or patch releases.)
|
Well spotted, cheers! |
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.
As documented in Composer's Basic Usage page,
the
composer.lock file must be commited to VCS. This file allows both package developers and end developer-users to keep fixed versionsof packages installed, preventing the installation of unsuported package versions.
This also helps preventing developers from unintentionally installing the latest version of a package which may also unintentionally contain breaking
changes.
If keeping dependencies up to date feels like a heavy chore, dependabot could help.