requirements-app.txt

# Run `make freeze-requirements` to update requirements.txt
# with package version changes made in requirements-app.txt

ago==0.0.93
humanize==2.2.0
Flask==1.1.1
Flask-WTF==0.14.3
Flask-Login==0.5.0

blinker==1.4
pyexcel==0.5.15
pyexcel-io==0.5.20
pyexcel-xls==0.5.8
pyexcel-xlsx==0.5.8
pyexcel-ods3==0.5.3
pytz==2019.3
gunicorn==20.0.4
eventlet==0.25.1
notifications-python-client==5.5.1

# PaaS
awscli-cwlogs>=1.4,<1.5
itsdangerous==1.1.0

git+https://github.com/alphagov/notifications-utils.git@36.12.0#egg=notifications-utils==36.12.0
git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.1-alpha#egg=govuk-frontend-jinja==0.5.1-alpha
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00			# Run `make freeze-requirements` to update requirements.txt
			`# with package version changes made in requirements-app.txt`

Update ago from 0.0.92 to 0.0.93 2018-10-06 20:15:33 +01:00			`ago==0.0.93`
Update humanize from 1.0.0 to 2.2.0 2020-03-30 14:49:04 +01:00			`humanize==2.2.0`
Update flask from 1.0.3 to 1.1.1 2019-08-26 14:43:06 +01:00			`Flask==1.1.1`
Update flask-wtf from 0.14.2 to 0.14.3 2020-02-10 13:47:05 +00:00			`Flask-WTF==0.14.3`
upgrade flask_login to 0.5.0 flask_login sets a bunch of variables in the session object. We only use one of them, `user_id`. We set that to the user id from the database, and refer to it all over the place. However, in flask_login 0.5.0 they prefix this with an underscore to prevent people accidentally overwriting it etc. So when a user logs in we need to make sure that we set user_id manually so we can still use it. flask_login sets a bunch of variables on the `flask.session` object. However, this session object isn't the one that gets passed in to the request context by flask - that one can only be modified outside of requests from within the session_transaction context manager (see [1]). So, flask_login populates the normal session and then we need to copy all of those values across. We didn't need to do this previously because we already set the `user_id` value on line 20 of tests/__init__.py, but now that flask_login is looking for `_user_id` instead we need to do this properly. [1] https://flask.palletsprojects.com/en/1.1.x/testing/#accessing-and-modifying-sessions 2020-03-06 15:41:13 +00:00			`Flask-Login==0.5.0`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
			`blinker==1.4`
Update pyexcel from 0.5.14 to 0.5.15 2019-08-26 14:43:08 +01:00			`pyexcel==0.5.15`
Update pyexcel-io from 0.5.18 to 0.5.20 2019-08-26 14:43:09 +01:00			`pyexcel-io==0.5.20`
Update pyexcel-xls from 0.5.7 to 0.5.8 2018-09-03 09:56:45 +01:00			`pyexcel-xls==0.5.8`
bump requirements 2020-01-21 14:21:48 +00:00			`pyexcel-xlsx==0.5.8`
Update pyexcel-ods3 from 0.5.2 to 0.5.3 2018-11-27 08:03:16 +00:00			`pyexcel-ods3==0.5.3`
Update pytz from 2019.2 to 2019.3 2019-11-04 13:48:06 +00:00			`pytz==2019.3`
bump reqs 2020-02-04 17:16:58 +00:00			`gunicorn==20.0.4`
Update eventlet from 0.25.0 to 0.25.1 2019-08-26 14:43:11 +01:00			`eventlet==0.25.1`
bump reqs 2020-02-04 17:16:58 +00:00			`notifications-python-client==5.5.1`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
			`# PaaS`
			`awscli-cwlogs>=1.4,<1.5`
Upgrade itsdangerous Version 1.1.0 has reverted the breaking change (moving from sha1 to sha256) that was introduced in version 1.0.0. Upgrading now so that we can take advantage of this bug fix: https://github.com/pallets/itsdangerous/issues/46 2020-02-19 13:47:35 +00:00			`itsdangerous==1.1.0`
Update notifications-utils to 30.5.6 This brings in the change to email validation which removes obscure white space from email addresses. 2018-10-29 10:21:04 +00:00
Refactor to use PostalAddress helper from utils Since we’re doing normalisation and line-count-checking of addresses in multiple places it makes sense for that code to be shared. Which is what happened here: https://github.com/alphagov/notifications-utils/pull/713 This commit refactors the admin code to make use of the new utils code. Note about placeholders: - they now go into the session as `address_line_1` instead of `address line 1` because this is the format the API uses, so should be considered canonical - they are now fetched from the session in a way that isn’t sensitive to case or underscores (using the `Columns` class) - the API doesn’t care about case or underscores vs spaces in placeholder names because it’s checking an instance of `Template` to see if all the required placeholders are present (see https://github.com/alphagov/notifications-api/blob/401c8e41d6a1e3b348b99eb0cc205bb420fce0c1/app/notifications/process_notifications.py#L40) 2020-04-02 17:21:27 +01:00			`git+https://github.com/alphagov/notifications-utils.git@36.12.0#egg=notifications-utils==36.12.0`
bump requirements 2020-01-21 14:21:48 +00:00			`git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.1-alpha#egg=govuk-frontend-jinja==0.5.1-alpha`