Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org> --- upgrading/5.x.x.txt | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 upgrading/5.x.x.txt diff --git a/upgrading/5.x.x.txt b/upgrading/5.x.x.txt new file mode 100644 index 0000000..ba74e28 --- /dev/null +++ b/upgrading/5.x.x.txt @@ -0,0 +1,4 @@ +Starting from release 5.0.0, Alembic is used for managing database migrations. + +Run `alembic upgrade head` from the aurweb root directory to upgrade your +database after upgrading the source code to a new release. -- 2.26.0
Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org> --- Add missing raw SQL upgrade instructions. upgrading/{4.9.0.txt => 5.x.x.txt} | 8 ++++++++ 1 file changed, 8 insertions(+) rename upgrading/{4.9.0.txt => 5.x.x.txt} (54%) diff --git a/upgrading/4.9.0.txt b/upgrading/5.x.x.txt similarity index 54% rename from upgrading/4.9.0.txt rename to upgrading/5.x.x.txt index 241f24a..94f91c6 100644 --- a/upgrading/4.9.0.txt +++ b/upgrading/5.x.x.txt @@ -1,3 +1,11 @@ +Starting from release 5.0.0, Alembic is used for managing database migrations. + +Run `alembic upgrade head` from the aurweb root directory to upgrade your +database after upgrading the source code to a new release. + +When upgrading from 4.8.0, you also need to execute the following manual SQL +statements before doing so. + 1. Add new columns to store the timestamp and UID when closing requests: ---- -- 2.26.0
participants (1)
-
Lukas Fleischer