Update the requirement the right way

Author: AlanCoding

requirements/requirements.in

@@ -3,7 +3,7 @@
 # if you are add a new feature which requires dependencies they should be in a separate requirements_<feature>.in file
 #
 cryptography
-Django<6.0
+Django>5.2.0,<6.0
 djangorestframework
 django-crum
 inflection

requirements/requirements_all.txt

@@ -24,7 +24,7 @@ defusedxml==0.8.0rc2
     # via
     #   python3-openid
     #   social-auth-core
-django==4.2.21
+django==5.2.7
     # via
     #   -r requirements/requirements.in
     #   channels

requirements/requirements_dev.txt

@@ -1,7 +1,7 @@
 ansible                 # Used in build process to generate some configs
 black==25.1.0           # Linting tool, if changed update pyproject.toml as well
 build
-django==4.2.21
+django==5.2.7
 django-debug-toolbar
 django-extensions
 djangorestframework

requirements/updater.sh

@@ -3,6 +3,14 @@ set -ue
 
 PYTHON=python3.11
 
+# Ensure script is run from the requirements/ directory
+if [[ "$(basename $(pwd))" != "requirements" ]]; then
+	echo "ERROR: This script must be run from the requirements/ directory"
+	echo "Current directory: $(pwd)"
+	echo "Please run: cd requirements && ./updater.sh [run|upgrade]"
+	exit 1
+fi
+
 for FILE in requirements.in requirements_all.txt ; do
 	if [ ! -f ${FILE} ] ; then
 		touch ${FILE}