Skip to content

Bump the dependencies group across 1 directory with 5 updates #3003

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 6, 2025

Bumps the dependencies group with 5 updates in the / directory:

Package From To
doctrine/orm 2.20.3 3.3.3
nelmio/api-doc-bundle 4.38.2 5.3.0
zircote/swagger-php 4.11.1 5.1.3
phpunit/phpcov 11.0.0 11.0.1
phpunit/phpunit 12.1.6 12.2.0

Updates doctrine/orm from 2.20.3 to 3.3.3

Release notes

Sourced from doctrine/orm's releases.

3.3.3

Release Notes for 3.3.3

3.3.x bugfix release (patch)

3.3.3

  • Total issues resolved: 0
  • Total pull requests resolved: 16
  • Total contributors: 5

Improvement

Bugfixes

Documentation

CI

This release contains the changes from https://github.com/doctrine/orm/releases/tag/2.20.3

3.3.2

Release Notes for 3.3.2

... (truncated)

Upgrade guide

Sourced from doctrine/orm's upgrade guide.

Upgrade to 3.4

Using the same class several times in a discriminator map is deprecated. In 4.0, this will be an error.

Upgrade to 3.3

Deprecate DatabaseDriver

The class Doctrine\ORM\Mapping\Driver\DatabaseDriver is deprecated without replacement.

Add Doctrine\ORM\Query\OutputWalker interface, deprecate Doctrine\ORM\Query\SqlWalker::getExecutor()

Output walkers should implement the new \Doctrine\ORM\Query\OutputWalker interface and create Doctrine\ORM\Query\Exec\SqlFinalizer instances instead of Doctrine\ORM\Query\Exec\AbstractSqlExecutors. The output walker must not base its workings on the query firstResult/maxResult values, so that the SqlFinalizer can be kept in the query cache and used regardless of the actual firstResult/maxResult values. Any operation dependent on firstResult/maxResult should take place within the SqlFinalizer::createExecutor() method. Details can be found at doctrine/orm#11188.

Upgrade to 3.2

Deprecate the NotSupported exception

The class Doctrine\ORM\Exception\NotSupported is deprecated without replacement.

Deprecate remaining Serializable implementation

Relying on SequenceGenerator implementing the Serializable is deprecated because that interface won't be implemented in ORM 4 anymore.

The following methods are deprecated:

  • SequenceGenerator::serialize()
  • SequenceGenerator::unserialize()

orm:schema-tool:update option --complete is deprecated

That option behaves as a no-op, and is deprecated. It will be removed in 4.0.

Deprecate properties $indexes and $uniqueConstraints of Doctrine\ORM\Mapping\Table

The properties $indexes and $uniqueConstraints have been deprecated since they had no effect at all. The preferred way of defining indices and unique constraints is by using the \Doctrine\ORM\Mapping\UniqueConstraint and \Doctrine\ORM\Mapping\Index attributes.

Upgrade to 3.1

Deprecate Doctrine\ORM\Mapping\ReflectionEnumProperty

... (truncated)

Commits
  • 1f1891d Merge pull request #11926 from greg0ire/3.3.x
  • c9fc4d9 Merge remote-tracking branch 'origin/2.20.x' into 3.3.x
  • 0e3cff0 Update composite-primary-keys.rst (#11919)
  • 5c50ed9 Merge pull request #11924 from xabbuh/dbal-6867
  • 5a1e560 prefer primary key constraints over Index::isPrimary()
  • 78e8887 Merge pull request #11911 from xabbuh/dbal-6890
  • 5eb298b Merge pull request #11914 from xabbuh/dbal-6886
  • 5eb0255 do not use deprecated index features
  • 28575f5 Merge pull request #11903 from xabbuh/dbal-6867
  • 457d2d2 do not use deprecated primary key constraint features
  • Additional commits viewable in compare view

Updates nelmio/api-doc-bundle from 4.38.2 to 5.3.0

Release notes

Sourced from nelmio/api-doc-bundle's releases.

v5.3.0

What's Changed

New Contributors

Full Changelog: nelmio/NelmioApiDocBundle@v5.2.1...v5.3.0

v5.2.1

What's Changed

Full Changelog: nelmio/NelmioApiDocBundle@v5.2.0...v5.2.1

v5.2.0

What's Changed

Full Changelog: nelmio/NelmioApiDocBundle@v5.1.0...v5.2.0

v5.1.0

What's Changed

Full Changelog: nelmio/NelmioApiDocBundle@v5.0.2...v5.1.0

v5.0.2

What's Changed

New Contributors

Full Changelog: nelmio/NelmioApiDocBundle@v5.0.1...v5.0.2

... (truncated)

Changelog

Sourced from nelmio/api-doc-bundle's changelog.

5.3.0

Added support for Symfony's TranslatableInterface

5.2.1

Fixed a bug where using abstract controllers would ignore various attributes like #[OA\Tag] & #[Security] on child classes

5.2.0

Made it possible to automatically generate security definitions based on the #[IsGranted] attribute.

nelmio_api_doc:
    # ...
areas:
    default:
        security:
            MyBearerScheme:
                type: 'http'
                scheme: 'bearer'

5.1.0

Made it possible to configure how operation ids are generated.

nelmio_api_doc:
    operation_id_generation: always_prepend

Possible values: always_prepend, conditionally_prepend, no_prepend or enum instance of Nelmio\ApiDocBundle\Describer\OperationIdGeneration

Commits

Updates zircote/swagger-php from 4.11.1 to 5.1.3

Release notes

Sourced from zircote/swagger-php's releases.

5.1.3

What's Changed

New Contributors

Full Changelog: zircote/swagger-php@5.1.2...5.1.3

5.1.2

What's Changed

New Contributors

Full Changelog: zircote/swagger-php@5.1.1...5.1.2

5.1.1

What's Changed

New Contributors

Full Changelog: zircote/swagger-php@5.1.0...5.1.1

5.1.0

What's Changed

New Contributors

... (truncated)

Commits

Updates phpunit/phpcov from 11.0.0 to 11.0.1

Changelog

Sourced from phpunit/phpcov's changelog.

[11.0.1] - 2025-02-29

  • No changes; phpcov.phar rebuilt with updated dependencies
Commits
  • 64bf2aa Prepare release
  • a1cad50 Update test fixture
  • 221f8dc Fix date
  • f761821 Fix issues identified by PHPStan
  • 6139502 Ignore errors related to using internals of phpunit/php-code-coverage
  • 7e19f1b Use PHPStan instead of Psalm and update CI workflow configuration
  • a91bd57 Update tools
  • cf5dfcf Expand documentation of PHAR download
  • See full diff in compare view

Updates phpunit/phpunit from 12.1.6 to 12.2.0

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 12.2.0

Added

Experimental Support for Open Test Reporting XML

PHPUnit has supported reporting test results in the JUnit XML format for a long time. Unfortunately, there has never been a standard schema for the JUnit XML format. Common consumers of Clover XML log files interpret these files differently, which has led to frequent problems.

To address this, the JUnit team started the Open Test Reporting project, creating and maintaining language-agnostic XML and HTML test reporting formats. Unlike JUnit XML, Open Test Reporting's XML formats are extensible.

Logging in the Open Test Reporting XML format is controlled by the new --log-otr CLI option and the new <otr> XML configuration element.

This feature is experimental and the generated XML may change in order to enhance compliance with the Open Test Reporting project's XML schema definitions. The same applies to the XML schema definitions for information that is specific for PHP and PHPUnit. Please note that such changes may occur in bugfix or minor releases and could potentially break backwards compatibility.

Experimental Support for OpenClover XML

PHPUnit has supported reporting code coverage information in the Clover XML format for a long time. Unfortunately, there has never been a standard schema for the Clover XML format. Common consumers of Clover XML log files interpret these files differently, which leads to frequent problems.

The original commercial Clover project has been superseded by the Open Source OpenClover project, which provides an XML schema for its OpenClover XML format. Rather than modifying the existing Clover XML reporter to comply with the OpenClover XML schema, thereby breaking backward compatibility, a new OpenClover XML reporter has been introduced.

This new reporter is controlled by the new CLI option, --coverage-openclover, and the new XML configuration element, <openclover>. This code coverage reporter generates XML documents that validate against the OpenClover project's XML schema definition, with one exception: the <testproject> element is not generated.

The existing Clover XML reporter, controlled by the --coverage-clover CLI option and the <clover> XML configuration element, remains unchanged.

This feature is experimental and the generated XML may change to enhance compliance with the OpenClover XML schema definition. Please note that such changes may occur in bugfix or minor releases and could potentially break backwards compatibility.

Miscellaneous

  • --with-telemetry CLI option that can be used together with --debug to print debugging information that includes telemetry information
  • The TestCase::provideAdditionalInformation() method can now be used to emit a Test\AdditionalInformationProvided event
  • The new Test\AfterLastTestMethodFailed, Test\AfterTestMethodFailed, Test\BeforeFirstTestMethodFailed, Test\BeforeTestMethodFailed, Test\PostConditionFailed, Test\PreConditionFailed events are now emitted instead of Test\AfterLastTestMethodErrored, Test\AfterTestMethodErrored, Test\BeforeFirstTestMethodErrored, Test\BeforeTestMethodErrored, Test\PostConditionErrored, Test\PreConditionErrored when the Throwable extends AssertionFailedError to distinguish between errors and failures triggered in hook methods
  • The new Test\PreparationErrored event is now emitted instead of Test\PreparationFailed when the Throwable does not extend AssertionFailedError to distinguish between errors and failures triggered during test preparation
  • Test\PreparationFailed::throwable()

Changed

  • #6165: Collect deprecations triggered by autoloading while loading/building the test suite
  • Do not treat warnings differently than other issues in summary section of default output
  • A warning is now emitted when both #[CoversNothing] and #[Covers*] (or #[Uses*]) are used on a test class
  • A warning is now emitted when the same #[Covers*] (or #[Uses*]) attribute is used multiple times on a test class
  • A warning is now emitted when the same code is targeted by both #[Covers*] and #[Uses*] attributes
  • A warning is now emitted when a hook method such as setUp(), for example has a #[Test] attribute
  • A warning is now emitted when more than one of #[Small], #[Medium], or #[Large] is used on a test class
  • A warning is now emitted when a data provider provides data sets that have more values than the test method consumes using arguments

How to install or update PHPUnit

Changelog

Sourced from phpunit/phpunit's changelog.

12.2.0 - 2025-06-06

Added

Experimental Support for Open Test Reporting XML

PHPUnit has supported reporting test results in the JUnit XML format for a long time. Unfortunately, there has never been a standard schema for the JUnit XML format. Common consumers of Clover XML log files interpret these files differently, which has led to frequent problems.

To address this, the JUnit team started the Open Test Reporting project, creating and maintaining language-agnostic XML and HTML test reporting formats. Unlike JUnit XML, Open Test Reporting's XML formats are extensible.

Logging in the Open Test Reporting XML format is controlled by the new --log-otr CLI option and the new <otr> XML configuration element.

This feature is experimental and the generated XML may change in order to enhance compliance with the Open Test Reporting project's XML schema definitions. The same applies to the XML schema definitions for information that is specific for PHP and PHPUnit. Please note that such changes may occur in bugfix or minor releases and could potentially break backwards compatibility.

Experimental Support for OpenClover XML

PHPUnit has supported reporting code coverage information in the Clover XML format for a long time. Unfortunately, there has never been a standard schema for the Clover XML format. Common consumers of Clover XML log files interpret these files differently, which leads to frequent problems.

The original commercial Clover project has been superseded by the Open Source OpenClover project, which provides an XML schema for its OpenClover XML format. Rather than modifying the existing Clover XML reporter to comply with the OpenClover XML schema, thereby breaking backward compatibility, a new OpenClover XML reporter has been introduced.

This new reporter is controlled by the new CLI option, --coverage-openclover, and the new XML configuration element, <openclover>. This code coverage reporter generates XML documents that validate against the OpenClover project's XML schema definition, with one exception: the <testproject> element is not generated.

The existing Clover XML reporter, controlled by the --coverage-clover CLI option and the <clover> XML configuration element, remains unchanged.

This feature is experimental and the generated XML may change to enhance compliance with the OpenClover XML schema definition. Please note that such changes may occur in bugfix or minor releases and could potentially break backwards compatibility.

Miscellaneous

  • --with-telemetry CLI option that can be used together with --debug to print debugging information that includes telemetry information
  • The TestCase::provideAdditionalInformation() method can now be used to emit a Test\AdditionalInformationProvided event
  • The new Test\AfterLastTestMethodFailed, Test\AfterTestMethodFailed, Test\BeforeFirstTestMethodFailed, Test\BeforeTestMethodFailed, Test\PostConditionFailed, Test\PreConditionFailed events are now emitted instead of Test\AfterLastTestMethodErrored, Test\AfterTestMethodErrored, Test\BeforeFirstTestMethodErrored, Test\BeforeTestMethodErrored, Test\PostConditionErrored, Test\PreConditionErrored when the Throwable extends AssertionFailedError to distinguish between errors and failures triggered in hook methods
  • The new Test\PreparationErrored event is now emitted instead of Test\PreparationFailed when the Throwable does not extend AssertionFailedError to distinguish between errors and failures triggered during test preparation
  • Test\PreparationFailed::throwable()

Changed

  • #6165: Collect deprecations triggered by autoloading while loading/building the test suite
  • Do not treat warnings differently than other issues in summary section of default output
  • A warning is now emitted when both #[CoversNothing] and #[Covers*] (or #[Uses*]) are used on a test class
  • A warning is now emitted when the same #[Covers*] (or #[Uses*]) attribute is used multiple times on a test class
  • A warning is now emitted when the same code is targeted by both #[Covers*] and #[Uses*] attributes
  • A warning is now emitted when a hook method such as setUp(), for example has a #[Test] attribute
  • A warning is now emitted when more than one of #[Small], #[Medium], or #[Large] is used on a test class
  • A warning is now emitted when a data provider provides data sets that have more values than the test method consumes using arguments
Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the dependencies group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [doctrine/orm](https://github.com/doctrine/orm) | `2.20.3` | `3.3.3` |
| [nelmio/api-doc-bundle](https://github.com/nelmio/NelmioApiDocBundle) | `4.38.2` | `5.3.0` |
| [zircote/swagger-php](https://github.com/zircote/swagger-php) | `4.11.1` | `5.1.3` |
| [phpunit/phpcov](https://github.com/sebastianbergmann/phpcov) | `11.0.0` | `11.0.1` |
| [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) | `12.1.6` | `12.2.0` |



Updates `doctrine/orm` from 2.20.3 to 3.3.3
- [Release notes](https://github.com/doctrine/orm/releases)
- [Upgrade guide](https://github.com/doctrine/orm/blob/3.3.x/UPGRADE.md)
- [Commits](doctrine/orm@2.20.3...3.3.3)

Updates `nelmio/api-doc-bundle` from 4.38.2 to 5.3.0
- [Release notes](https://github.com/nelmio/NelmioApiDocBundle/releases)
- [Changelog](https://github.com/nelmio/NelmioApiDocBundle/blob/5.x/CHANGELOG.md)
- [Commits](nelmio/NelmioApiDocBundle@v4.38.2...v5.3.0)

Updates `zircote/swagger-php` from 4.11.1 to 5.1.3
- [Release notes](https://github.com/zircote/swagger-php/releases)
- [Commits](zircote/swagger-php@4.11.1...5.1.3)

Updates `phpunit/phpcov` from 11.0.0 to 11.0.1
- [Changelog](https://github.com/sebastianbergmann/phpcov/blob/main/ChangeLog.md)
- [Commits](sebastianbergmann/phpcov@11.0.0...11.0.1)

Updates `phpunit/phpunit` from 12.1.6 to 12.2.0
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/12.2.0/ChangeLog-12.2.md)
- [Commits](sebastianbergmann/phpunit@12.1.6...12.2.0)

---
updated-dependencies:
- dependency-name: doctrine/orm
  dependency-version: 3.3.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: nelmio/api-doc-bundle
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: zircote/swagger-php
  dependency-version: 5.1.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: phpunit/phpcov
  dependency-version: 11.0.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: phpunit/phpunit
  dependency-version: 12.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file php Pull requests that update Php code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants