Skip to content

chore(deps): commit Composer locks for the package and WordPress fixture - #14

Merged
brianvarskonst merged 1 commit into
mainfrom
chore/commit-composer-lock
Oct 25, 2026
Merged

brianvarskonst merged 1 commit into
mainfrom
chore/commit-composer-lock

Conversation

@brianvarskonst

Copy link
Copy Markdown
Member

Summary

Commits composer.lock for the package and for the WordPress integration fixture, so CI and contributors install the same verified dependency set.

  • Root lock: the shared QA workflow already validates strictly, installs from a present lock and runs 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 update found nothing newer within the constraints.
  • Fixture lock: tests/WordPress/composer.lock was gitignored and stale locally (Symfony YAML 8.1.8 despite the ^8.1.6 security 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.
  • Stable path package: the fixture's path repository reports the package as dev-main with a config-based reference, so the fixture lock no longer changes with every commit or branch name.

Checklist

  • The change is focused and scoped to one concern.
  • Tests or verification notes are included for behavior changes.
  • Documentation was added or updated where needed.
  • Public APIs, configuration keys, and contracts are described clearly.
  • Backward compatibility impact is noted.

Type of Change

  • Bug fix
  • Feature
  • Documentation
  • Refactoring
  • Maintenance
  • Breaking change

Verification

From empty vendor/ directories inside DDEV:

  • Root: composer install from the lock (90 packages), composer validate --strict --no-check-publish, composer audit --locked (no advisories), composer qa green.
  • Fixture: tests/WordPress/setup.sh installs from the lock (44 packages), composer audit --locked clean, tests/WordPress/run.sh passes all checks on WordPress 7.1.3.
  • After committing, composer update --dry-run in the fixture reports nothing to modify.

Notes

  • No consumer impact: library locks are not used by dependents, so no release is needed.
  • All SymPress dependencies are public, so the secret-less WordPress integration job downloads them without authentication.

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.
@brianvarskonst
brianvarskonst merged commit 2a3dfbd into main Oct 25, 2026
4 checks passed
@brianvarskonst
brianvarskonst deleted the chore/commit-composer-lock branch October 25, 2026 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant