Skip to content

Comments

Pin django-pipeline to a recent version#664

Merged
knabar merged 1 commit intoome:masterfrom
knabar:maint-pin-django-pipeline
Feb 10, 2026
Merged

Pin django-pipeline to a recent version#664
knabar merged 1 commit intoome:masterfrom
knabar:maint-pin-django-pipeline

Conversation

@knabar
Copy link
Member

@knabar knabar commented Feb 6, 2026

As per Tom's suggestion, pin django-pipeline in setup.py to force a recent version

@knabar knabar added this to the 5.31.0 milestone Feb 6, 2026
@knabar knabar requested a review from will-moore February 6, 2026 12:39
@knabar knabar self-assigned this Feb 6, 2026
Copy link
Member

@sbesson sbesson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use this opportunity to also review django-redis and either relax the pinning to a >=5.3.0 or even move towards django-redis 6?

Copy link
Member

@sbesson sbesson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the official statement about Django 5.2 support in https://github.com/jazzband/django-pipeline/releases/tag/4.1.0, defining this as the minimal version is consistent with #646

@knabar
Copy link
Member Author

knabar commented Feb 10, 2026

Should we use this opportunity to also review django-redis and either relax the pinning to a >=5.3.0 or even move towards django-redis 6?

Addressed in #665

@knabar knabar merged commit 3346bda into ome:master Feb 10, 2026
8 checks passed
@knabar knabar deleted the maint-pin-django-pipeline branch February 13, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants