Bump doctrine/doctrine-fixtures-bundle from 3.6.1 to 4.0.0

[dependabot]

Bumps doctrine/doctrine-fixtures-bundle from 3.6.1 to 4.0.0.

Release notes

Sourced from doctrine/doctrine-fixtures-bundle's releases.

4.0.0

Release Notes for 4.0.0

Backwards incompatible release (major)

4.0.0

• Total issues resolved: 0
• Total pull requests resolved: 11
• Total contributors: 3

Breaking changes

• 483: Tag dependency injection classes as internal thanks to @​greg0ire
• 480: Make final classes that can be thanks to @​greg0ire
• 470: Remove deprecation thanks to @​greg0ire
• 409: Add native return types everywhere thanks to @​derrabus

Dependencies

• 471: Drop support for doctrine/data-fixtures 1 thanks to @​greg0ire
• 396: Bumping min Symfony version to 5.4, php version to 8.1 thanks to @​weaverryan
• 395: Allow symfony 7 dependencies thanks to @​weaverryan

Static Analysis

• 473: Remove baseline thanks to @​greg0ire
• 469: Make PurgerFactory generic thanks to @​greg0ire

Internal

• 478: Upgrade to PHPUnit 11 thanks to @​greg0ire
• 412: Apply PHPCS' PHP 8.1 rules thanks to @​derrabus

3.7.1

Release Notes for 3.7.1

3.7.x bugfix release (patch)

3.7.1

• Total issues resolved: 0
• Total pull requests resolved: 8
• Total contributors: 3

Bugfix

• 475: Add missing psr/log requirement thanks to @​greg0ire

... (truncated)

Upgrade guide

Sourced from doctrine/doctrine-fixtures-bundle's upgrade guide.

UPGRADE to 4.0

Type declarations

Type declarations have been added everywhere. Types extending or implementing types from this bundle need to be updated to match the new signatures.

Final classes

Some classes have been marked as final because they are not supposed to be extended. Consider using composition instead of inheritance.

Mandatory ManagerRegistry argument

It is now mandatory to pass a ManagerRegistry instance to the constructor of Doctrine\Bundle\FixturesBundle\Command\LoadDataFixturesDoctrineCommand.

UPGRADE to 3.0

• The automatic loading of fixtures in a directory (e.g. AppBundle\DataFixtures\ORM) was removed. Instead, register your fixture classes as services and tag them with doctrine.fixture.orm, like this:

# src/AppBundle/Resources/config/dataFixture.yml
services:
  _defaults:
    tags: ['doctrine.fixture.orm']
    autowire: true # if you need dependency injection, see next bullet point
AppBundle\DataFixtures\ORM:
resource: '../../DataFixtures/ORM/*'

This will happen automatically if you're using the Symfony 3.3 or higher default service configuration and your fixture classes extend the normal Doctrine\Bundle\FixturesBundle\Fixture class, or implement the new Doctrine\Bundle\FixturesBundle\ORMFixtureInterface.

• The base Fixture class no longer implements ContainerAwareInterface and so no longer have a $this->container property. You can manually implement this interface. Or, a better idea is to update your fixtures to use dependency injection:

class MyFixture extends Fixture
{
</tr></table> 

... (truncated)

Commits

• 9018531 Merge pull request #484 from doctrine/3.7.x-merge-up-into-4.0.x_sAXZ3QlL
• ebfb3a5 Merge pull request #473 from greg0ire/reduce-baseline
• 920e483 Merge pull request #483 from greg0ire/internal
• aa28cd3 Add missing type declarations and phpdoc
• ab66f79 Tag dependency injection classes as internal
• b2b9bfa Merge pull request #480 from greg0ire/finalize
• bd59519 Merge pull request #482 from olberger/patch-1
• 33bc99a Add 2nd parameter (class) to getReference() call
• be1bc35 Merge pull request #481 from doctrine/3.7.x
• 8fb5791 Merge pull request #478 from greg0ire/phpunit-11
• Additional commits viewable in compare view

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 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)

[mickel1138]

@dependabot rebase

[mickel1138]

Skip for now, will do with all the other Doctrine upgrades.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.