chore(deps-dev): bump pytest-django from 4.11.1 to 4.12.0#5875
Merged
chore(deps-dev): bump pytest-django from 4.11.1 to 4.12.0#5875
Conversation
Bumps [pytest-django](https://github.com/pytest-dev/pytest-django) from 4.11.1 to 4.12.0. - [Release notes](https://github.com/pytest-dev/pytest-django/releases) - [Changelog](https://github.com/pytest-dev/pytest-django/blob/main/docs/changelog.rst) - [Commits](pytest-dev/pytest-django@v4.11.1...v4.12.0) --- updated-dependencies: - dependency-name: pytest-django dependency-version: 4.12.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
rtibblesbot
approved these changes
May 1, 2026
Contributor
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
Dependency Update Review
Package: pytest-django 4.11.1 → 4.12.0
Semver risk: Minor
Dependency type: Dev dependency (requirements-dev.txt)
CI status: Linting passes; Python unit tests in progress at time of review
Changelog Analysis
Sources consulted:
- PR body (sourced from pytest-django changelog)
- Commits v4.11.1…v4.12.0
Breaking changes: None. Dropped Python 3.9 support — project runs Python 3.10, unaffected.
Other notable changes:
- Python 3.14 and Django 6.0 officially supported
- Multi-database support promoted from experimental to stable
- New
@pytest.mark.django_isolate_appsmark anddjango_isolated_appsfixture (additive, no migration needed)
Compatibility Assessment
- Project Python version: 3.10 — meets new minimum ✓
- Peer dependency changes: none
- Code changes required: none
- Prior failed attempts: none noted
Recommendation
APPROVE — minor dev dependency update with no breaking changes for this project. Verify Python unit tests pass after they complete.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
rtibbles
approved these changes
May 1, 2026
Member
rtibbles
left a comment
rtibbles
left a comment
There was a problem hiding this comment.
No concerns from changelog, and tests still pass for test only dependency.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps pytest-django from 4.11.1 to 4.12.0.
Changelog
Sourced from pytest-django's changelog.
Commits
a2a9495Release 4.12.0020bc23tests: make sure access to default can also be blockedbcefbe8Add support for isolating apps in tests39c8dccplugin: add a note why we reorder tests1830acdpyproject.toml: require pytest 9 for self tests, switch to native toml config...f19da08Fix the order of the test cases that use the live_server fixture92858eedocs: add pytest 9.0+ native TOML configuration format3f550d9build(deps): bump hynek/build-and-inspect-python-package1f50dd2Drop obsolete traces of Django 5.0 in CI247ec1cFixPytestCollectionWarningforTestRunnerclass (#1259)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)