Repository navigation
chore(deps): commit Composer lock - #50
Merged
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
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.
Summary
Commits
composer.lockso CI and contributors install the same verified dependency set.composer update(103 packages); SymPress dependencies are at their newest tags (sympress/coding-standardsv1.1.1,sympress/kernelv1.1.13,sympress/qav0.1.3), Symfony v8.1.9..gitignore: drops thecomposer.lockentry so the lock is tracked.Type of Change
Verification
From an empty
vendor/inside DDEV (PHP 8.5.9, Composer 2.10.3):composer installfrom the lock,composer validate --strict --no-check-publish,composer audit --locked(no advisories),composer qagreen.examples/siteis a documented manifest, not an installed fixture:tools/smoke-examples.pycopies it into a temporary project and installs it fresh against this checkout, so it gets no lock.Notes