Merge pull request #1634 from openhealthcare/dependabot/pip/letter-0.5

Bump letter from 0.4.1 to 0.5

changelog.md

@@ -13,7 +13,8 @@ Note: This will requires a migration to be created for all applications.
 Introduces two new Angular filters: `displayDate` and `displayDateTime`. These format a date
 for display according to the setting `DATE_DISPLAY_FORMAT`. This defaults to `D MMM YYYY`.
 
-New applications will have this setting in their scaffold, existing applications may wish to add it.
+New applications will have this setting in their scaffold, existing applications may wish to add
+it.
 
 All core Opal templates that previously used `shortDate` or `shortDateTime` have been updated to
 use either `displayDate` or `displayDateTime`.
@@ -71,15 +72,14 @@ This change is not accompanied by a retrospective migration so your existing fk_
 stored in a case sensitive manner. It is recommended you migrate all of your fk_or_ft fields
 as this will give you consistent behaviour.
 
-##### For example.
+##### For example
 
 Prior to this change if I had an allergy for "paracetomol" but an entry in the models.Drug
 table of "Paracetomol", it would be stored as free text in the `Allergies.drug` field, because
 it was case sensitive. Going forward after this change it will be saved as a foreign key. This
 change will not be made retrospecively however so you would need to add a migration that resaved
 the Allergies.drug.
 
-
 #### Misc Changes
 
 * The undocumented Reopen Episode flow included in Opal < 0.8.0 has now been completely removed,
@@ -89,6 +89,10 @@ including the `reopen_episode_modal.html` template and the url/view at `template
 
 * Adds in a footer updated/created by to the form base template
 
+#### Updates to the Dependency Graph
+
+* Letter: 0.4.1 -> 0.5
+
 
 ### 0.12.0 (Major Release)
 

doc/docs/reference/upgrading.md

@@ -5,13 +5,41 @@ application to a later version where there are extra steps required.
 
 ### 0.13.0 -> 0.12.0 - 0.11.2
 
+#### Upgrading Opal
+
+How you do this depends on how you have configured your application. You will need to
+update both the Opal version, and versions of upgraded dependencies if
+you have specified them in for instance, a requirements.txt.
+
+(This will be the case if you use the requirements.txt originally provided by
+`opal startproject`)
+
+    # requirements.txt
+    opal==0.10.0
+    letter==0.5
+
 #### Free text or foreign key fields are now, by default case insensitive
 
 It is recommended you resave all model values for fk_or_ft fields as this will give you
 consistent behaviour. Otherwise fk_ft values wihch differ from fkt values only by
 case prior to this upgrade will be stored as ft and those afterwards will be stored as
 the relevant fk.
 
+
+#### Migrations
+
+You will need to run the migrations for Opal 0.13.0
+
+    $ python manage.py migrate opal
+
+As Opal 0.13.0 contains changes to the definition of lookuplists, you will
+need to run a makemigrations command to update your lookuplists to enable code
+values and change case sensitivity.
+
+    python manage.py makemigrations yourapp
+    python manage.py migrate yourapp
+
+
 ### 0.11.1 -> 0.11.2
 
 This bugfix release should be entirely backwards compatible.

opal/scaffolding/scaffold/requirements.txt.jinja2

@@ -9,7 +9,7 @@ dj-static==0.0.6
 django-reversion==1.10.2
 django-axes==1.7.0
 ffs==0.0.8.2
-letter==0.4.1
+letter==0.5
 requests==2.18.4
 djangorestframework==3.4.7
 django-compressor==2.2

setup.py

@@ -46,7 +46,7 @@
     },
     install_requires=[
         'ffs>=0.0.8.2',
-        'letter==0.4.1',
+        'letter==0.5',
         'jinja2==2.10',
         'requests==2.18.4',
         'django==1.10.8',