Upgraded to latest dependencies (CS) as per #62, locked dependencies …

…via `composer.lock` By commiting `composer.lock`, we can ensure reproducible builds for tools that change often and otherwise break everything at the slightles improvement or regression (PHPCS, Psalm). Our tests still verify upgrades via runtime tests, so we're still OK with running `composer update`, just not when static analysis and code style checks run, because those are way too fragile. Signed-Off-By: Marco Pivetta <[email protected]>
laminas · Dec 9, 2020 · 9a08941 · 9a08941
1 parent 131153f
commit 9a08941
Show file tree

Hide file tree

Showing 3 changed files with 4,410 additions and 4 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1,6 +1,5 @@
 /.phpunit.result.cache
 /clover.xml
-/composer.lock
 /coveralls-upload.json
 /docs/html/
 /laminas-mkdoc-theme.tgz

diff --git a/composer.json b/composer.json
@@ -26,11 +26,11 @@
     "require-dev": {
         "ext-phar": "*",
         "doctrine/annotations": "^1.10.4",
-        "laminas/laminas-coding-standard": "^1.0.0",
+        "laminas/laminas-coding-standard": "^2.1.4",
         "laminas/laminas-stdlib": "^3.3.0",
         "phpunit/phpunit": "^9.4.2",
-        "psalm/plugin-phpunit": "^0.13.0",
-        "vimeo/psalm": "^4.2"
+        "psalm/plugin-phpunit": "^0.14.0",
+        "vimeo/psalm": "^4.3.1"
     },
     "conflict": {
         "phpspec/prophecy": "<1.9.0"