Updated pipfile.lock

[NiallEgan]

I regenerated the Pipfile.lock using pipenv lock command. I think we should be more careful in future to ensure that the lock does not get out of date.

---

This change is 

[riaJha97]

Reviewed 2 of 2 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @NiallEgan and @mrniket)

---

Pipfile, line 9 at r1 (raw file):

[packages]
"e1839a8" = {editable = true, path = "."}

Was the order an issue before?

[OlafSzmidt]

Should this perhaps be automatic in our deployment pipelines?

Reviewed 2 of 2 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @NiallEgan and @mrniket)

[NiallEgan]

I am looking in to this, but is complicated because of the way we are currently deploying aimmo, portal and rr.

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @NiallEgan)

---

Pipfile, line 9 at r1 (raw file):

Previously, riaJha97 wrote…

Was the order an issue before?

No, this was randomly changed when I regenerated the Pipfile.

[OlafSzmidt]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @riaJha97)