chore(deps-dev): bump pytest-factoryboy from 2.1.0 to 2.7.0

[dependabot]

Bumps pytest-factoryboy from 2.1.0 to 2.7.0.

Changelog

Sourced from pytest-factoryboy's changelog.

Changelog

Unreleased

• Declare required python version >= 3.8. (python 3.7 support was already removed in 2.6.0, the declared supported version tag was not updated though). [#215](https://github.com/pytest-dev/pytest-factoryboy/issues/215) <https://github.com/pytest-dev/pytest-factoryboy/pull/215>_

2.6.1

• Address compatibility issue with pytest 8.1. [#213](https://github.com/pytest-dev/pytest-factoryboy/issues/213) <https://github.com/pytest-dev/pytest-bdd/pull/213>_

2.6.0

• Drop python 3.7 support and add support for python 3.12. Supported versions are now: 3.8, 3.9, 3.10, 3.11, 3.12. [#197](https://github.com/pytest-dev/pytest-factoryboy/issues/197) <https://github.com/pytest-dev/pytest-factoryboy/pull/197>_
• Drop support for pytest `_

2.5.1

• Fix PytestDeprecationWarning. [#180](https://github.com/pytest-dev/pytest-factoryboy/issues/180) <https://github.com/pytest-dev/pytest-factoryboy/pull/180>_ [#179](https://github.com/pytest-dev/pytest-factoryboy/issues/179) <https://github.com/pytest-dev/pytest-factoryboy/issues/179>_

2.5.0

• Using a generic class container like dict, list, set, etc. will raise a warning suggesting you to wrap your model using named_model(...). Doing this will make sure that the fixture name is correctly chosen, otherwise SubFactory and RelatedFactory aren't able to determine the name of the model. See Generic Container Classes as models <https://pytest-factoryboy.readthedocs.io/en/latest/#generic-container-classes-as-models>_ [#167](https://github.com/pytest-dev/pytest-factoryboy/issues/167) <https://github.com/pytest-dev/pytest-factoryboy/pull/167>_
• Fix Factory._after_postgeneration being invoked twice. [#164](https://github.com/pytest-dev/pytest-factoryboy/issues/164) <https://github.com/pytest-dev/pytest-factoryboy/pull/164>_ [#156](https://github.com/pytest-dev/pytest-factoryboy/issues/156) <https://github.com/pytest-dev/pytest-factoryboy/issues/156>_
• Stack traces caused by pytest-factoryboy are now slimmer. [#169](https://github.com/pytest-dev/pytest-factoryboy/issues/169) <https://github.com/pytest-dev/pytest-factoryboy/pull/169>_
• Check for naming conflicts between factory and model fixture name, and raise a clear error immediately. [#86](https://github.com/pytest-dev/pytest-factoryboy/issues/86) <https://github.com/pytest-dev/pytest-factoryboy/pull/86>_

2.4.0

• LazyFixture is now a Generic[T] type.
• Simplify fixture generation (internal change).
• Use poetry (internal change).

2.3.1

• Fix AttributeError when using LazyFixture in register(...) [#159](https://github.com/pytest-dev/pytest-factoryboy/issues/159) <https://github.com/pytest-dev/pytest-factoryboy/issues/159>_ [#158](https://github.com/pytest-dev/pytest-factoryboy/issues/158) <https://github.com/pytest-dev/pytest-factoryboy/issues/158>_

2.3.0

• Add support for factory.PostGenerationMethodCall [#103](https://github.com/pytest-dev/pytest-factoryboy/issues/103) <https://github.com/pytest-dev/pytest-factoryboy/pull/103>_ [#87](https://github.com/pytest-dev/pytest-factoryboy/issues/87) <https://github.com/pytest-dev/pytest-factoryboy/issues/87>_.

2.2.1

• @register() decorator now refuses kwargs after the initial specialization. This behaviour was mistakenly introduced in version 2.2.0, and it complicates the usage of the register function unnecessarily. For example, the following is not allowed anymore:

.. code-block:: python

# INVALID

... (truncated)

Commits

• See full diff 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)