Bump the minor group across 1 directory with 4 updates - #188
Merged
Conversation
Bumps the minor group with 4 updates in the / directory: [django](https://github.com/django/django), [google-cloud-logging](https://github.com/googleapis/google-cloud-python), [newrelic](https://github.com/newrelic/newrelic-python-agent) and [uvicorn](https://github.com/Kludex/uvicorn). Updates `django` from 6.0.7 to 6.1 - [Commits](django/django@6.0.7...6.1) Updates `google-cloud-logging` from 3.16.1 to 3.16.2 - [Release notes](https://github.com/googleapis/google-cloud-python/releases) - [Changelog](https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-documentai/CHANGELOG.md) - [Commits](googleapis/google-cloud-python@google-cloud-logging-v3.16.1...google-cloud-logging-v3.16.2) Updates `newrelic` from 13.3.0 to 13.4.0 - [Release notes](https://github.com/newrelic/newrelic-python-agent/releases) - [Commits](newrelic/newrelic-python-agent@v13.3.0...v13.4.0) Updates `uvicorn` from 0.51.0 to 0.52.1 - [Release notes](https://github.com/Kludex/uvicorn/releases) - [Changelog](https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md) - [Commits](Kludex/uvicorn@0.51.0...0.52.1) --- updated-dependencies: - dependency-name: django dependency-version: '6.1' dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor - dependency-name: google-cloud-logging dependency-version: 3.16.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor - dependency-name: newrelic dependency-version: 13.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor - dependency-name: uvicorn dependency-version: 0.52.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor ... Signed-off-by: dependabot[bot] <support@github.com>
django-ninja 1.6.2 pins Django<6.1, which made this PR's own Django 6.1
bump fail dependency resolution during the Docker build:
ERROR: Cannot install ... because these package versions have
conflicting dependencies.
The conflict is caused by:
The user requested django==6.1
django-ninja 1.6.2 depends on Django<6.1 and >=3.1
1.6.3 drops that upper bound entirely (Django>=3.1, no cap per PyPI's
requires_dist), so bumping it alongside django closes the gap.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Hf6j2xXQXywHVh3HAVRxB3
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
1 participant
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.
Summary
Supersedes #174, which was failing CI: it bumped
djangoto 6.1, butdjango-ninja==1.6.2pinsDjango<6.1, so the Docker build'spip installfailed dependency resolution outright. #174 was also stale (opened before #184 merged and removedtypogrify/Jinja2fromrequirements.txt), which is what made it show as conflicting.django6.0.7→6.1,google-cloud-logging3.16.1→3.16.2,newrelic13.3.0→13.4.0,uvicorn0.51.0→0.52.1) onto currentmain.django-ninja1.6.2→1.6.3, which drops theDjango<6.1cap entirely (Django>=3.1, no upper bound per PyPI) -- the actual unblock for the Django 6.1 bump.Test plan
docker compose build testssucceeds (previously failed withResolutionImpossible).docker compose run --rm tests-- all 152 tests pass.Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
https://claude.ai/code/session_01Hf6j2xXQXywHVh3HAVRxB3