oncall-engine/engine/requirements-dev.in

-c requirements.txt
celery-types==0.18.0
django-filter-stubs==0.1.3
django-stubs[compatible-mypy]==4.2.2
djangorestframework-stubs[compatible-mypy]==3.14.2
httpretty==1.1.4
mypy==1.4.1
pre-commit==2.15.0
pytest==8.2.2
pytest-django==4.8.0
pytest-xdist[psutil]==3.6.1
pytest_factoryboy==2.7.0
types-beautifulsoup4==4.12.0.5
types-PyMySQL==1.0.19.7
types-python-dateutil==2.8.19.13
types-requests==2.31.0.1
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where all deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements). 2024-02-20 14:44:15 -03:00			`-c requirements.txt`
			`celery-types==0.18.0`
			`django-filter-stubs==0.1.3`
			`django-stubs[compatible-mypy]==4.2.2`
			`djangorestframework-stubs[compatible-mypy]==3.14.2`
			`httpretty==1.1.4`
			`mypy==1.4.1`
			`pre-commit==2.15.0`
bump `uwsgi` to 2.0.26 + Python to 3.12.3 (#4495) # What this PR does - bumps `uwsgi` to latest version (`2.0.26`), which unblocks us from bumping Python to 3.12 - bumps Python to 3.12.3 - refactor the Snyk GitHub Actions workflow to use the composable actions for installed frontend and backend dependencies - fixes several `AttributeError`s in our tests that went from a warning to an error in Python 3.12 (see https://github.com/python/cpython/issues/100690) # Which issue(s) this PR closes Closes #4358 Closes https://github.com/grafana/oncall/issues/4387 2024-06-10 15:33:37 -04:00			`pytest==8.2.2`
			`pytest-django==4.8.0`
			`pytest-xdist[psutil]==3.6.1`
			`pytest_factoryboy==2.7.0`
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where all deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements). 2024-02-20 14:44:15 -03:00			`types-beautifulsoup4==4.12.0.5`
			`types-PyMySQL==1.0.19.7`
			`types-python-dateutil==2.8.19.13`
			`types-requests==2.31.0.1`