There are new versions of your dependencies available!
Package
Current Version
New Version
codeception/codeception
2.1.4
2.3.3
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version.
If you have a test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update. Please take a look on the above section if you rely on the composer.lock file for your tests
If you don't have a test suite (you should), you can checkout to this branch (git checkout dependenci17691) and make sure everything is working.
About tests that rely on the composer.lock file
DependenCI doesn't currently support auto-updating the composer.lock file. If your tests do `composer install` instead of `composer update`, you'll have to manually update the composer.lock file. You can run `composer update nothing --lock` to update your lockfile.
Want to disable checking for a specific dependency?
You can add an excluded section into your composer.json to exclude some dependencies from the analysis.
Your composer.json would look like this:
```
{
"name": "maba/webpack-bundle",
"description": "Bundle to Integrate Webpack to Symfony",
"keywords": [
"webpack",
"assets",
"symfony",
"symfony2",
"amd",
"commonjs"
],
"license": "MIT",
"authors": [
{
"name": "Marius Balčytis",
"email": "marius.balcytis@gmail.com"
}
],
"require": {
"php": "^5.3.2 || >=7.0 <7.2",
"symfony/framework-bundle": "^2.7|^3.0",
"symfony/templating": "^2.1|^3.0",
"symfony/console": "^2.5|^3.0",
"symfony/routing": "^2.7|^3.0",
"twig/twig": "^1.27|^2.0",
"maba/dependency-injection-extra": "^0.1.1",
"symfony/process": "^2.5|^3.0",
"symfony/dependency-injection": "^2.6|^3.0",
"symfony/twig-bundle": "^2.3|^3.0",
"symfony/monolog-bundle": "^2.3|^3.0"
},
"require-dev": {
"friendsofphp/php-cs-fixer": "^2.2",
"symfony/framework-bundle": "^2.7.1|^3.0",
"codeception/codeception": "^2.3.3",
"symfony/translation": "^2.7|^3.0",
"symfony/asset": "^2.7|^3.0",
"doctrine/annotations": "^1.0"
},
"autoload": {
"psr-4": {
"Maba\\Bundle\\WebpackBundle\\": "src"
}
},
"autoload-dev": {
"psr-4": {
"Fixtures\\Maba\\Bundle\\": "tests/functional/Fixtures/src"
}
},
"minimum-stability": "dev",
"extra": {
"dependenci": {
"excluded": [
"excluded/dependency"
]
}
}
}
```
Not sure how things should work exactly?
If you need help, have a cool idea for DependenCI or just want to say hi, drop us a mail at [dependenci@miguelpiedrafita.com](mailto:dependenci@miguelpiedrafita.com).
There are new versions of your dependencies available!
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version. If you have a test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update. Please take a look on the above section if you rely on the
composer.lockfile for your tests If you don't have a test suite (you should), you can checkout to this branch (git checkout dependenci17691) and make sure everything is working.About tests that rely on the composer.lock file
DependenCI doesn't currently support auto-updating the composer.lock file. If your tests do `composer install` instead of `composer update`, you'll have to manually update the composer.lock file. You can run `composer update nothing --lock` to update your lockfile.Want to disable checking for a specific dependency?
You can add an excluded section into your composer.json to exclude some dependencies from the analysis. Your composer.json would look like this: ``` { "name": "maba/webpack-bundle", "description": "Bundle to Integrate Webpack to Symfony", "keywords": [ "webpack", "assets", "symfony", "symfony2", "amd", "commonjs" ], "license": "MIT", "authors": [ { "name": "Marius Balčytis", "email": "marius.balcytis@gmail.com" } ], "require": { "php": "^5.3.2 || >=7.0 <7.2", "symfony/framework-bundle": "^2.7|^3.0", "symfony/templating": "^2.1|^3.0", "symfony/console": "^2.5|^3.0", "symfony/routing": "^2.7|^3.0", "twig/twig": "^1.27|^2.0", "maba/dependency-injection-extra": "^0.1.1", "symfony/process": "^2.5|^3.0", "symfony/dependency-injection": "^2.6|^3.0", "symfony/twig-bundle": "^2.3|^3.0", "symfony/monolog-bundle": "^2.3|^3.0" }, "require-dev": { "friendsofphp/php-cs-fixer": "^2.2", "symfony/framework-bundle": "^2.7.1|^3.0", "codeception/codeception": "^2.3.3", "symfony/translation": "^2.7|^3.0", "symfony/asset": "^2.7|^3.0", "doctrine/annotations": "^1.0" }, "autoload": { "psr-4": { "Maba\\Bundle\\WebpackBundle\\": "src" } }, "autoload-dev": { "psr-4": { "Fixtures\\Maba\\Bundle\\": "tests/functional/Fixtures/src" } }, "minimum-stability": "dev", "extra": { "dependenci": { "excluded": [ "excluded/dependency" ] } } } ```Not sure how things should work exactly?
If you need help, have a cool idea for DependenCI or just want to say hi, drop us a mail at [dependenci@miguelpiedrafita.com](mailto:dependenci@miguelpiedrafita.com).Powered by DependenCI :octocat: