darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-05-01 22:51:10 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
6f95e4e0ca4d44f44f16ecf2f7cfd0a4e49ca66c
notifications-admin/requirements.in

37 lines
1.3 KiB
Plaintext
Raw Normal View History

Copy requirements files to .in We’re going to move to using pip-tools for freezing requirements. pip-tools uses `.in` files for the un-frozen list of requirements, and then generates `.txt` equivalents. This commit just copies our existing `.txt` files, keeping the same name but giving them a `.in` extension ready for pip-tools to use.
2020-12-29 13:07:22 +00:00
# Run `make freeze-requirements` to update requirements.txt
# with package version changes made in requirements-app.txt
ago==0.0.93
Update govuk-bank-holidays from 0.10 to 0.11
2022-03-02 14:42:02 +00:00
govuk-bank-holidays==0.11
Update humanize from 3.12.0 to 4.0.0 Breaking change is due to dropping support for Python 3.6.
2022-03-02 14:45:18 +00:00
humanize==4.0.0
Pin Flask to less than version 2 Flask 2.0 requires Jinja 3.0 govuk_frontend_jinja is not compatible with Jinja 3.0 yet
2021-06-02 15:24:38 +01:00
Flask==1.1.2 # pyup: <2
Update flask-wtf from 1.0.0 to 1.0.1
2022-04-06 09:25:32 +01:00
Flask-WTF==1.0.1
Update wtforms from 3.0.0 to 3.0.1
2022-03-02 14:51:37 +00:00
wtforms==3.0.1
Update minor and patch versions of some core dependencies
2022-05-05 13:43:45 +01:00
Flask-Login==0.6.1
Pin Werkzeug to below 2.1.x We can’t upgrade to Werkzeug 2.1.0 because the `BaseResponse` class has been renamed. The old version of Flask we are using tries to import `BaseResponse` causing an error. See https://github.com/pallets/werkzeug/issues/1963
2022-05-05 14:08:11 +01:00
werkzeug==2.0.3 # Can’t be upgraded until we are using Flask >= 2
Pin Jinja to below 3.1.x We can’t upgrade to Jinja 3.1.0 because the `escape` module has been moved to the `markupsafe` library. The old version of Flask we are using tries to import `escape` from `jinja2`, causing an error. See https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-0
2022-05-05 14:01:36 +01:00
jinja2==3.0.3 # Can’t be upgraded until we are using Flask >= 2
Copy requirements files to .in We’re going to move to using pip-tools for freezing requirements. pip-tools uses `.in` files for the un-frozen list of requirements, and then generates `.txt` equivalents. This commit just copies our existing `.txt` files, keeping the same name but giving them a `.in` extension ready for pip-tools to use.
2020-12-29 13:07:22 +00:00
blinker==1.4
Update pyexcel from 0.6.7 to 0.7.0
2022-04-06 10:30:53 +01:00
pyexcel==0.7.0
Update pyexcel-io from 0.6.5 to 0.6.6
2022-03-02 14:56:06 +00:00
pyexcel-io==0.6.6
Update pyexcel-xls from 0.6.2 to 0.7.0
2021-10-18 14:56:08 +01:00
pyexcel-xls==0.7.0
Copy requirements files to .in We’re going to move to using pip-tools for freezing requirements. pip-tools uses `.in` files for the un-frozen list of requirements, and then generates `.txt` equivalents. This commit just copies our existing `.txt` files, keeping the same name but giving them a `.in` extension ready for pip-tools to use.
2020-12-29 13:07:22 +00:00
pyexcel-xlsx==0.6.0
Bump pyexcel-ods3 to 0.6.1
2022-04-06 13:42:20 +01:00
pyexcel-ods3==0.6.1
Update pytz from 2021.3 to 2022.1
2022-04-06 09:37:27 +01:00
pytz==2022.1
pin gunicorn to support newer version of eventlet this is consistent with notifications api https://github.com/alphagov/notifications-api/pull/3466
2022-03-03 11:16:24 +00:00
# Should be pinned until a new gunicorn release greater than 20.1.0 comes out. (Due to eventlet v0.33 compatibility issues)
git+https://github.com/benoitc/gunicorn.git@1299ea9e967a61ae2edebe191082fd169b864c64#egg=gunicorn[eventlet]==20.1.0
Bump python-client to 6.3.0
2021-10-11 12:26:56 +01:00
notifications-python-client==6.3.0
Use pure Python Rtree library The Python rtree library we are using to build RTrees has a dependency on the C package libspatialindex. This package is not installed on PaaS, so it’s hard for us to use it. This commit changes the code to use a library called rtreelib instead. rtreelib doesn’t have a built in way to serialise the index it builds, so I’ve had to implement that using pickle.
2021-04-13 12:43:28 +01:00
rtreelib==0.2.0
remove cryptography pin we previously pinned cryptography to versions less than 3.4 since after that point, cryptography started using rust as a dependency. This isn't an issue if you install from wheel, but we found that the version of pip bundled with the python buildpack was too old to support this. However, since upgrading from python 3.6 to python 3.9, the pip version has been bumped and we now no longer need to pin cryptography as it installs correctly.
2022-01-19 18:27:41 +00:00
fido2==0.9.3
Update minor and patch versions of some core dependencies
2022-05-05 13:43:45 +01:00
pyproj==3.3.1
Copy requirements files to .in We’re going to move to using pip-tools for freezing requirements. pip-tools uses `.in` files for the un-frozen list of requirements, and then generates `.txt` equivalents. This commit just copies our existing `.txt` files, keeping the same name but giving them a `.in` extension ready for pip-tools to use.
2020-12-29 13:07:22 +00:00
# PaaS
awscli-cwlogs>=1.4,<1.5
Pin Flask to less than version 2 Flask 2.0 requires Jinja 3.0 govuk_frontend_jinja is not compatible with Jinja 3.0 yet
2021-06-02 15:24:38 +01:00
itsdangerous==1.1.0 # pyup: <2
Bump utils to 55.1.6 Brings in: - [x] https://github.com/alphagov/notifications-utils/pull/966/files
2022-04-26 16:40:22 +01:00
notifications-utils @ git+https://github.com/alphagov/notifications-utils.git@55.1.6
Don’t put version number in requirements twice It’s a pain having to remember to update both of them. Looks like `pip` now supports a different syntax without the `egg` bit which means a git dependency only needs the version number changing in one place.
2021-11-23 11:27:12 +00:00
govuk-frontend-jinja @ git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.8-alpha
Copy requirements files to .in We’re going to move to using pip-tools for freezing requirements. pip-tools uses `.in` files for the un-frozen list of requirements, and then generates `.txt` equivalents. This commit just copies our existing `.txt` files, keeping the same name but giving them a `.in` extension ready for pip-tools to use.
2020-12-29 13:07:22 +00:00
# gds-metrics requires prometheseus 0.2.0, override that requirement as later versions bring significant performance gains
Unpin prometheus-client and use the latest version The prometheus-client was pinned to avoid installing version 0.10.0, which removed support for `prometheus_multiproc_dir` and renamed the variable `PROMETHEUS_MULTIPROC_DIR`. Version 0.10.1 reintroduced support for the lowercase `prometheus_multiproc_dir` environment variable.
2022-04-06 13:44:10 +01:00
prometheus-client==0.14.0
Use our own fork of gds_metrics_python and add shared auth token This will allow both prometheis (the shared one and our own) to scrape the /metrics endpoint, each with their own authentication See alphagov/gds_metrics_python#1 for more details
2022-04-21 15:30:03 +03:00
git+https://github.com/alphagov/gds_metrics_python.git@6f1840a57b6fb1ee40b7e84f2f18ec229de8aa72
Reference in New Issue Copy Permalink