Bump doctrine/doctrine-fixtures-bundle from 3.7.1 to 4.1.0

[dependabot]

Bumps doctrine/doctrine-fixtures-bundle from 3.7.1 to 4.1.0.

Release notes

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

4.1.0

Release Notes for 4.1.0

Feature release (minor)

4.1.0

• Total issues resolved: 0
• Total pull requests resolved: 2
• Total contributors: 2

Improvement

• 495: Add support for persistence 4 thanks to @​greg0ire
• 489: Drop support for Symfony 5 thanks to @​derrabus

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

... (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

• a06db6b Merge pull request #505 from doctrine/4.0.x
• f83d498 Merge pull request #504 from greg0ire/4.0.x
• d283290 Merge remote-tracking branch 'origin/3.7.x' into 4.0.x
• 78e2448 Merge pull request #501 from doctrine/dependabot/composer/3.7.x/doctrine/codi...
• ff70a86 Update doctrine/coding-standard requirement from 12.0.0 to 13.0.0
• 00739dc Update symfony/phpunit-bridge requirement from 6.4.16 to 7.2.0 (#503)
• b8bef49 Update phpstan/phpstan requirement from 2.1.8 to 2.1.11 (#502)
• 6bb5328 Merge pull request #497 from greg0ire/dependabot-php
• ac08178 Merge pull request #495 from greg0ire/persistence-4-compat
• 73ae542 Merge pull request #500 from doctrine/4.0.x
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

This PR is stale because it has been open 40 days with no activity.