# Testing Django beta downgrades several dependencies

**URL:** <https://forum.djangoproject.com/t/testing-django-beta-downgrades-several-dependencies/32663>\
**Category:** Deployment\
**Created:** [July 3, 2024, 12:18pm UTC](https://forum.djangoproject.com/t/testing-django-beta-downgrades-several-dependencies/32663 "2024-07-03T12:18:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cclauss](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/cclauss/32/10185_2.png) [@cclauss](https://forum.djangoproject.com/u/cclauss)\
**Post date:** [July 3, 2024, 12:18pm UTC](https://forum.djangoproject.com/t/testing-django-beta-downgrades-several-dependencies/32663/1 "2024-07-03T12:18:12Z")

</div>

Our project runs Django v5.0.6 successfully in production.

When I attempt to test the project on [Django v5.1.0-beta-1](https://pypi.org/project/Django/5.1b1) several key dependencies are _ **downgraded** _. Why the _ **downgrades** _?

```auto
django-celery-beat: 2.6.0 --> 2.1.0
django-honeypot: 1.2.0 --> 0.9.0
django-tenants: 3.6.1 --> 1.1.6
django-timezone-field: 6.1.0 --> 4.2.3

```

- [Start testing on Django v5.1 by cclauss · Pull Request #761 · celery/django-celery-beat · GitHub](https://github.com/celery/django-celery-beat/pull/761)
- [Start testing on Django v5.1 by cclauss · Pull Request #103 · jamesturk/django-honeypot · GitHub](https://github.com/jamesturk/django-honeypot/pull/103)
- [Start testing on Django v5.1 by cclauss · Pull Request #1061 · django-tenants/django-tenants · GitHub](https://github.com/django-tenants/django-tenants/pull/1061)
- [Start testing on Django v5.1 by cclauss · Pull Request #128 · mfogel/django-timezone-field · GitHub](https://github.com/mfogel/django-timezone-field/pull/128)

---

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [July 3, 2024, 12:51pm UTC](https://forum.djangoproject.com/t/testing-django-beta-downgrades-several-dependencies/32663/2 "2024-07-03T12:51:29Z")

</div>

As you’ve identified from those links, those are all third-party projects.

These aren’t Django issues - it’s up to the maintainers of those projects to update them as appropriate.

(It is not that Django depends upon a specific version of those packages, it is that those packages depend upon specific versions of Django.)

---

<div class="post-metadata">

**Author:** ![cclauss](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/cclauss/32/10185_2.png) [@cclauss](https://forum.djangoproject.com/u/cclauss)\
**Post date:** [July 8, 2024, 1:45pm UTC](https://forum.djangoproject.com/t/testing-django-beta-downgrades-several-dependencies/32663/3 "2024-07-08T13:45:16Z")

</div>

Thanks. I am starting to understand that Upper Bound Version Constraints do not scale to large numbers of dependencies… [Should You Use Upper Bound Version Constraints? -](https://iscinumpy.dev/post/bound-version-constraints/)