Repository navigation
chore(deps): commit Composer locks for the package and WordPress fixture - #14
Merged
Merged
Conversation
Track composer.lock so CI and contributors install the same verified dependency set; QA already validates strictly, installs from the lock and runs a locked audit when one is present. The WordPress fixture lock was gitignored and stale locally (Symfony YAML 8.1.8, Kernel 1.1.0); it now pins WordPress 7.1.3, Symfony 8.1.9, Kernel 1.1.13 and Framework Bundle 1.0.8. The path repository reports the package as dev-main with a config-based reference, so the fixture lock does not change per commit or branch.
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.lockfor the package and for the WordPress integration fixture, so CI and contributors install the same verified dependency set.composer audit --locked. Every SymPress dependency is locked at its newest tag (Kernel v1.1.13, Framework Bundle v1.0.8, Coding Standards v1.1.1, QA v0.1.3);composer updatefound nothing newer within the constraints.tests/WordPress/composer.lockwas gitignored and stale locally (Symfony YAML 8.1.8 despite the^8.1.6security floor, Kernel 1.1.0, Framework Bundle 1.0.1). It now pins WordPress 7.1.3, Symfony 8.1.9, Kernel 1.1.13 and Framework Bundle 1.0.8.dev-mainwith a config-based reference, so the fixture lock no longer changes with every commit or branch name.Checklist
Type of Change
Verification
From empty
vendor/directories inside DDEV:composer installfrom the lock (90 packages),composer validate --strict --no-check-publish,composer audit --locked(no advisories),composer qagreen.tests/WordPress/setup.shinstalls from the lock (44 packages),composer audit --lockedclean,tests/WordPress/run.shpasses all checks on WordPress 7.1.3.composer update --dry-runin the fixture reports nothing to modify.Notes