Skip to content
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

chore(deps-dev): bump pytest-factoryboy from 2.1.0 to 2.7.0 in /backend in the pytest group #8

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 13, 2024

Bumps the pytest group in /backend with 1 update: pytest-factoryboy.

Updates 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

Dependabot compatibility score

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

@dependabot dependabot bot requested a review from a team as a code owner May 13, 2024 07:39
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels May 13, 2024
@dependabot dependabot bot force-pushed the dependabot/pip/backend/pytest-496f24aafa branch 5 times, most recently from 1fc99be to b561ef7 Compare May 14, 2024 19:22
Bumps the pytest group in /backend with 1 update: [pytest-factoryboy](https://github.com/pytest-dev/pytest-factoryboy).


Updates `pytest-factoryboy` from 2.1.0 to 2.7.0
- [Changelog](https://github.com/pytest-dev/pytest-factoryboy/blob/master/CHANGES.rst)
- [Commits](https://github.com/pytest-dev/pytest-factoryboy/commits)

---
updated-dependencies:
- dependency-name: pytest-factoryboy
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pytest
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/pip/backend/pytest-496f24aafa branch from b561ef7 to b38e445 Compare May 15, 2024 10:50
Copy link
Contributor Author

dependabot bot commented on behalf of github May 20, 2024

Looks like pytest-factoryboy is updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this May 20, 2024
@dependabot dependabot bot deleted the dependabot/pip/backend/pytest-496f24aafa branch May 20, 2024 10:41
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 python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants