Changelog
*Sourced from [symfony/phpunit-bridge's changelog](https://github.com/symfony/phpunit-bridge/blob/master/CHANGELOG.md).*
> 5.0.0
> -----
>
> * removed `weak_vendor` mode, use `max[self]=0` instead
>
> 4.4.0
> -----
>
> * made the bridge act as a polyfill for newest PHPUnit features
> * added `SetUpTearDownTrait` to allow working around the `void` return-type added by PHPUnit 8
> * added namespace aliases for PHPUnit < 6
>
> 4.3.0
> -----
>
> * added `ClassExistsMock`
> * bumped PHP version from 5.3.3 to 5.5.9
> * split simple-phpunit bin into php file with code and a shell script
>
> 4.1.0
> -----
>
> * Search for `SYMFONY_PHPUNIT_VERSION`, `SYMFONY_PHPUNIT_REMOVE`,
> `SYMFONY_PHPUNIT_DIR` env var in `phpunit.xml` then in `phpunit.xml.dist`
>
> 4.0.0
> -----
>
> * support for the `testLegacy` prefix in method names to mark a test as legacy
> has been dropped, use the `@group legacy` notation instead
> * support for the `Legacy` prefix in class names to mark tests as legacy has
> been dropped, use the `@group legacy` notation instead
> * support for passing an array of mocked namespaces not indexed by the mock
> feature to the constructor of the `SymfonyTestsListenerTrait` class was
> dropped
>
> 3.4.0
> -----
>
> * added a `CoverageListener` to enhance the code coverage report
> * all deprecations but those from tests marked with `@group legacy` are always
> displayed when not in `weak` mode
>
> 3.3.0
> -----
>
> * using the `testLegacy` prefix in method names to mark a test as legacy is
> deprecated, use the `@group legacy` notation instead
> * using the `Legacy` prefix in class names to mark a test as legacy is deprecated,
> use the `@group legacy` notation instead
> ... (truncated)
Commits
- See full diff in [compare view](https://github.com/symfony/phpunit-bridge/commits/v5.0.0)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Updates the requirements on symfony/phpunit-bridge to permit the latest version.
Changelog
*Sourced from [symfony/phpunit-bridge's changelog](https://github.com/symfony/phpunit-bridge/blob/master/CHANGELOG.md).* > 5.0.0 > ----- > > * removed `weak_vendor` mode, use `max[self]=0` instead > > 4.4.0 > ----- > > * made the bridge act as a polyfill for newest PHPUnit features > * added `SetUpTearDownTrait` to allow working around the `void` return-type added by PHPUnit 8 > * added namespace aliases for PHPUnit < 6 > > 4.3.0 > ----- > > * added `ClassExistsMock` > * bumped PHP version from 5.3.3 to 5.5.9 > * split simple-phpunit bin into php file with code and a shell script > > 4.1.0 > ----- > > * Search for `SYMFONY_PHPUNIT_VERSION`, `SYMFONY_PHPUNIT_REMOVE`, > `SYMFONY_PHPUNIT_DIR` env var in `phpunit.xml` then in `phpunit.xml.dist` > > 4.0.0 > ----- > > * support for the `testLegacy` prefix in method names to mark a test as legacy > has been dropped, use the `@group legacy` notation instead > * support for the `Legacy` prefix in class names to mark tests as legacy has > been dropped, use the `@group legacy` notation instead > * support for passing an array of mocked namespaces not indexed by the mock > feature to the constructor of the `SymfonyTestsListenerTrait` class was > dropped > > 3.4.0 > ----- > > * added a `CoverageListener` to enhance the code coverage report > * all deprecations but those from tests marked with `@group legacy` are always > displayed when not in `weak` mode > > 3.3.0 > ----- > > * using the `testLegacy` prefix in method names to mark a test as legacy is > deprecated, use the `@group legacy` notation instead > * using the `Legacy` prefix in class names to mark a test as legacy is deprecated, > use the `@group legacy` notation instead > ... (truncated)Commits
- See full diff in [compare view](https://github.com/symfony/phpunit-bridge/commits/v5.0.0)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)