#10730 updated the core Django version to 5.2 lts. As part of this update, the minimum required python version has been increased to 3.11.
+
#10730 updated the core Django version to 5.2 lts.
+
+
As part of this update, the following breaking changes have been introduced:
+
+
PostgreSQL 14
+
+
The minimum supported version of PostgreSQL has been increased to 14. This means that users running PostgreSQL 13 will need to perform a manual update of their database in order to continue using InvenTree with the latest version. For more information, please refer to our update guide for a walkthrough of the database update procedure.
+
+
Python 3.11
+
The minimum supported python version has been increased to 3.11. This means that users running Python 3.10 or earlier will need to update their python installation in order to run InvenTree 1.2.0.
For users running with a PostgreSQL database, Django 5.2 requires a minimum version of PostgreSQL 14. This means that users running PostgreSQL 13 will need to perform a manual update of their database in order to continue using InvenTree with the latest version.
+
+
If you are attempting to update to InvenTree 1.2.0 while still running PostgreSQL 13, you will encounter the following error message:
+
+
django.db.utils.NotSupportedError: PostgreSQL 14 or later is required (found 13.23).
+
+
+
In such a case, you will need to perform a database update procedure to migrate your existing database from PostgreSQL 13 to PostgreSQL 14 (or later). This process involves backing up your existing database, installing the new version of PostgreSQL, and then restoring your data into the new database.
+
+
Migration Guide
+
+
Our documentation provides a detailed database migration guide to assist users with this process. We recommend that users perform a backup of their database before attempting the migration, and follow the instructions carefully to ensure a smooth transition to the new database version.
+
+
Following is an example of the steps involved in migrating an InvenTree installation from a PostgreSQL 13 database to a PostgreSQL 17 database, in the context of a docker installation. The same principles apply for non-docker installations, but the particular commands may differ.
+
+
PostgreSQL 17 is recommended as the target version, as it is supported by both the 1.1.x and 1.2.x versions of InvenTree.
+
+
Starting Conditions
+
+
The starting conditions for this migration are as follows:
The InvenTree version is pinned to 1.1.12 in the .env file
+
The database is running PostgreSQL 13 (set via the docker-compose.yml file).
+
+
+
+
+
+
+
We also have a data directory, external to the docker containers, with the following structure:
+
+
+
+
Target Conditions
+
+
The new installation will be running InvenTree 1.2.0 with PostgreSQL 17
+
+
Step 1. Perform Backup
+
+
The first step is to perform a backup of the existing database. This step must be performed with the old setup (postgres 13 / InvenTree 1.1.12), before we perform any updates to the software.
+
+
First, let’s confirm that we are running the expected version of InvenTree (1.1.12).
+
+
+
+
To perform the backup, we run the following command:
+
+
docker compose run --rm inventree-server invoke backup
+
+
+
This will create a backup of the database and media files in the data/backup directory.
+
+
Confirm that the backup files have been created before continuing to the next step.
+
+
Step 2. Move Database Directory
+
+
The PostgreSQL database files are stored in the data/pgdb directory. We need to remove these files, as they are specific to PostgreSQL 13 and will not be compatible with PostgreSQL 17. Rather than deleting them, we will move them to a backup location, just in case we need to revert back to the old setup.
+
+
mv data/pgdb data/pgdb_backup
+
+
+
Confirm that the pgdb directory has been moved to the backup location before continuing to the next step. The pgdb directory should no longer exist in the data directory.
+
+
Step 3. Update PostgreSQL Version
+
+
Next, we need to update the PostgreSQL version in the docker-compose.yml file. Change the version from 13 to 17:
+
+
+
+
Pull down the updated docker images:
+
+
docker compose pull
+
+
+
Step 4. Restore Data from Backup
+
+
Now we can restore the data from the backup we created previously, into the new PostgreSQL 17 database. Run the following commands:
+
+
docker compose run --rm inventree-server invoke migrate
+docker compose run --rm inventree-server invoke restore
+
+
+
This will restore the database and media files from the backup we created previously.
+
+
Step 5. Update InvenTree Version
+
+
Next, we need to update the InvenTree version in the .env file. Change the version from 1.1.12 to 1.2.0:
+
+
+
+
Then, we need to pull down the updated InvenTree server image:
+
+
docker compose pull
+
+
+
Next, run the InvenTree update procedure:
+
+
docker compose run --rm inventree-server invoke update
+
+
+
Step 6. Verify New Setup
+
+
Finally, we can start the new setup and verify that everything is working as expected.
+
+
docker compose up -d
+
+
+
Then, you should be able to access your InvenTree instance again, and confirm that you are running the new version (1.2.0):
+
+
+
+
We can also see that the correct versions of both PostgreSQL and InvenTree are running in the docker containers:
+
+
+
+
Step 7. Celebrate!
+
+
Congratulations! You have successfully migrated your InvenTree installation to the latest version, with an updated PostgreSQL database. You can now enjoy the new features and improvements that come with InvenTree 1.2.0, while also benefiting from the enhanced performance and security of PostgreSQL 17.
+
+
Please consider sponsoring the project, to help us continue to maintain and improve InvenTree for all users. Your support is greatly appreciated!
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/blog/feed.atom b/blog/feed.atom
index 92213e21..61296c55 100644
--- a/blog/feed.atom
+++ b/blog/feed.atom
@@ -1,4 +1,4 @@
-Jekyll2026-02-14T20:39:42+00:00/blog/feed.atomInvenTreeInvenTree is an open-source inventory management system which provides intuitive parts management and stock control. It is at the center of an ecosystem of addins for EDA tools, API wrapper, deeply integrated plugins and 3rd party tools.1.2.0 Release2026-02-12T00:00:00+00:002026-02-12T00:00:00+00:00/blog/2026/02/12/1.2.0The InvenTree team is excited to announce the release of version 1.2.0. Attention: This release has no support for PostgreSQL 13 - our docs contain information regading PostgreSQL updates. At least PostgreSQL 14 is required, we recommend PostgreSQL 18.
+Jekyll2026-02-14T23:57:44+00:00/blog/feed.atomInvenTreeInvenTree is an open-source inventory management system which provides intuitive parts management and stock control. It is at the center of an ecosystem of addins for EDA tools, API wrapper, deeply integrated plugins and 3rd party tools.1.2.0 Release2026-02-12T00:00:00+00:002026-02-12T00:00:00+00:00/blog/2026/02/12/1.2.0The InvenTree team is excited to announce the release of version 1.2.0. Attention: This release has no support for PostgreSQL 13 - our docs contain information regading PostgreSQL updates. At least PostgreSQL 14 is required, we recommend PostgreSQL 18.
This release includes numerous new features, improvements, and bug fixes.
@@ -16,7 +16,16 @@
Django Update
-
#10730 updated the core Django version to 5.2 lts. As part of this update, the minimum required python version has been increased to 3.11.
+
#10730 updated the core Django version to 5.2 lts.
+
+
As part of this update, the following breaking changes have been introduced:
+
+
PostgreSQL 14
+
+
The minimum supported version of PostgreSQL has been increased to 14. This means that users running PostgreSQL 13 will need to perform a manual update of their database in order to continue using InvenTree with the latest version. For more information, please refer to our update guide for a walkthrough of the database update procedure.
+
+
Python 3.11
+
The minimum supported python version has been increased to 3.11. This means that users running Python 3.10 or earlier will need to update their python installation in order to run InvenTree 1.2.0.
API changes
@@ -90,7 +99,130 @@
If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.
]]>SchrodingersGat1.1.0 Release2025-11-02T00:00:00+00:002025-11-02T00:00:00+00:00/blog/2025/11/02/1.1.0The InvenTree team is excited to announce the release of version 1.1.0.
+
]]>SchrodingersGatDatabase Update Procedure2026-02-12T00:00:00+00:002026-02-12T00:00:00+00:00/blog/2026/02/12/db-updateIn our recent 1.2.0 release, we updated our underlying django version to from 4.2 to 5.2.
+
+
For users running with a PostgreSQL database, Django 5.2 requires a minimum version of PostgreSQL 14. This means that users running PostgreSQL 13 will need to perform a manual update of their database in order to continue using InvenTree with the latest version.
+
+
If you are attempting to update to InvenTree 1.2.0 while still running PostgreSQL 13, you will encounter the following error message:
+
+
django.db.utils.NotSupportedError: PostgreSQL 14 or later is required (found 13.23).
+
+
+
In such a case, you will need to perform a database update procedure to migrate your existing database from PostgreSQL 13 to PostgreSQL 14 (or later). This process involves backing up your existing database, installing the new version of PostgreSQL, and then restoring your data into the new database.
+
+
Migration Guide
+
+
Our documentation provides a detailed database migration guide to assist users with this process. We recommend that users perform a backup of their database before attempting the migration, and follow the instructions carefully to ensure a smooth transition to the new database version.
+
+
Following is an example of the steps involved in migrating an InvenTree installation from a PostgreSQL 13 database to a PostgreSQL 17 database, in the context of a docker installation. The same principles apply for non-docker installations, but the particular commands may differ.
+
+
PostgreSQL 17 is recommended as the target version, as it is supported by both the 1.1.x and 1.2.x versions of InvenTree.
+
+
Starting Conditions
+
+
The starting conditions for this migration are as follows:
The InvenTree version is pinned to 1.1.12 in the .env file
+
The database is running PostgreSQL 13 (set via the docker-compose.yml file).
+
+
+
+
+
+
+
We also have a data directory, external to the docker containers, with the following structure:
+
+
+
+
Target Conditions
+
+
The new installation will be running InvenTree 1.2.0 with PostgreSQL 17
+
+
Step 1. Perform Backup
+
+
The first step is to perform a backup of the existing database. This step must be performed with the old setup (postgres 13 / InvenTree 1.1.12), before we perform any updates to the software.
+
+
First, let’s confirm that we are running the expected version of InvenTree (1.1.12).
+
+
+
+
To perform the backup, we run the following command:
+
+
docker compose run --rm inventree-server invoke backup
+
+
+
This will create a backup of the database and media files in the data/backup directory.
+
+
Confirm that the backup files have been created before continuing to the next step.
+
+
Step 2. Move Database Directory
+
+
The PostgreSQL database files are stored in the data/pgdb directory. We need to remove these files, as they are specific to PostgreSQL 13 and will not be compatible with PostgreSQL 17. Rather than deleting them, we will move them to a backup location, just in case we need to revert back to the old setup.
+
+
mv data/pgdb data/pgdb_backup
+
+
+
Confirm that the pgdb directory has been moved to the backup location before continuing to the next step. The pgdb directory should no longer exist in the data directory.
+
+
Step 3. Update PostgreSQL Version
+
+
Next, we need to update the PostgreSQL version in the docker-compose.yml file. Change the version from 13 to 17:
+
+
+
+
Pull down the updated docker images:
+
+
docker compose pull
+
+
+
Step 4. Restore Data from Backup
+
+
Now we can restore the data from the backup we created previously, into the new PostgreSQL 17 database. Run the following commands:
+
+
docker compose run --rm inventree-server invoke migrate
+docker compose run --rm inventree-server invoke restore
+
+
+
This will restore the database and media files from the backup we created previously.
+
+
Step 5. Update InvenTree Version
+
+
Next, we need to update the InvenTree version in the .env file. Change the version from 1.1.12 to 1.2.0:
+
+
+
+
Then, we need to pull down the updated InvenTree server image:
+
+
docker compose pull
+
+
+
Next, run the InvenTree update procedure:
+
+
docker compose run --rm inventree-server invoke update
+
+
+
Step 6. Verify New Setup
+
+
Finally, we can start the new setup and verify that everything is working as expected.
+
+
docker compose up -d
+
+
+
Then, you should be able to access your InvenTree instance again, and confirm that you are running the new version (1.2.0):
+
+
+
+
We can also see that the correct versions of both PostgreSQL and InvenTree are running in the docker containers:
+
+
+
+
Step 7. Celebrate!
+
+
Congratulations! You have successfully migrated your InvenTree installation to the latest version, with an updated PostgreSQL database. You can now enjoy the new features and improvements that come with InvenTree 1.2.0, while also benefiting from the enhanced performance and security of PostgreSQL 17.
+
+
Please consider sponsoring the project, to help us continue to maintain and improve InvenTree for all users. Your support is greatly appreciated!
]]>SchrodingersGat1.1.0 Release2025-11-02T00:00:00+00:002025-11-02T00:00:00+00:00/blog/2025/11/02/1.1.0The InvenTree team is excited to announce the release of version 1.1.0.
This is the first major update since our 1.0.0 stable release, and includes numerous new features, improvements, and bug fixes to enhance your experience with InvenTree.
]]>SchrodingersGat0.16.8 Release2024-11-07T00:00:00+00:002024-11-07T00:00:00+00:00/blog/2024/11/07/0.16.8We have just released version 0.16.8 which includes a patch for a critical bug in the InvenTree package installer.
-
-
We recommend that users upgrade to this version as soon as possible.
-
-
Missing Translation Files
-
-
Some users were experiencing reports of missing translation files when installing InvenTree using the package installer. The issue was identified and resolved in this release. Refer to the release notes (linked below) for more information.
]]>SchrodingersGat
\ No newline at end of file
diff --git a/extend/app.html b/extend/app.html
index db38bd5f..1f40a6fe 100644
--- a/extend/app.html
+++ b/extend/app.html
@@ -313,6 +313,22 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/functions.html b/functions.html
index 9655bfe0..17952e3e 100644
--- a/functions.html
+++ b/functions.html
@@ -222,6 +222,22 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/lippoliv.html b/lippoliv.html
index bf3b6299..fe4f8b74 100644
--- a/lippoliv.html
+++ b/lippoliv.html
@@ -30,11 +30,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"With over 15 years of experience and big big passion I learned to take care about the details. They build up to the big picture we have in mind. I’m planning ahead & act early to prevent a big bang.","headline":"Lippoliv","mainEntityOfPage":{"@type":"WebPage","@id":"/lippoliv"},"url":"/lippoliv"}
diff --git a/lippoliv/inventree-default-salesorder-items.html b/lippoliv/inventree-default-salesorder-items.html
index 1779d4c5..8a4e1cf4 100644
--- a/lippoliv/inventree-default-salesorder-items.html
+++ b/lippoliv/inventree-default-salesorder-items.html
@@ -31,11 +31,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"lippoliv"},"dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"Add default parts (configurable) to every newly created sales order automatically.","headline":"Inventree Default Salesorder Items","mainEntityOfPage":{"@type":"WebPage","@id":"/lippoliv/inventree-default-salesorder-items"},"url":"/lippoliv/inventree-default-salesorder-items"}
diff --git a/matmair.html b/matmair.html
index 4ede3011..21c29731 100644
--- a/matmair.html
+++ b/matmair.html
@@ -30,11 +30,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"I try to build an ecosystem of reusable plugins and integrations for InvenTree. Code once and KISS!","headline":"Matmair","mainEntityOfPage":{"@type":"WebPage","@id":"/matmair"},"url":"/matmair"}
diff --git a/matmair/inventree-apprise.html b/matmair/inventree-apprise.html
index dbef4014..3dbbe638 100644
--- a/matmair/inventree-apprise.html
+++ b/matmair/inventree-apprise.html
@@ -31,11 +31,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"matmair"},"dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"Send notifications from InvenTree via Apprise","headline":"Inventree Apprise","mainEntityOfPage":{"@type":"WebPage","@id":"/matmair/inventree-apprise"},"url":"/matmair/inventree-apprise"}
diff --git a/matmair/inventree-rapidoc.html b/matmair/inventree-rapidoc.html
index 78c2c19b..c1b1970c 100644
--- a/matmair/inventree-rapidoc.html
+++ b/matmair/inventree-rapidoc.html
@@ -31,11 +31,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"matmair"},"dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"Use RapiDoc for Inventree API docs.","headline":"Inventree Rapidoc","mainEntityOfPage":{"@type":"WebPage","@id":"/matmair/inventree-rapidoc"},"url":"/matmair/inventree-rapidoc"}
diff --git a/matmair/inventree-zapier.html b/matmair/inventree-zapier.html
index 945e5676..af2b1c29 100644
--- a/matmair/inventree-zapier.html
+++ b/matmair/inventree-zapier.html
@@ -31,11 +31,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"matmair"},"dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"Integrate Zapier into InvenTree","headline":"Inventree Zapier","mainEntityOfPage":{"@type":"WebPage","@id":"/matmair/inventree-zapier"},"url":"/matmair/inventree-zapier"}
diff --git a/melektron.html b/melektron.html
index dcb1a966..692de29f 100644
--- a/melektron.html
+++ b/melektron.html
@@ -30,11 +30,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"Juggling with bits and bytes for fun and profit ;) (and also electrons if I feel like it)","headline":"Melektron","mainEntityOfPage":{"@type":"WebPage","@id":"/melektron"},"url":"/melektron"}
diff --git a/melektron/inventree-adv-sheet-label.html b/melektron/inventree-adv-sheet-label.html
index fb4c3283..ea3f712a 100644
--- a/melektron/inventree-adv-sheet-label.html
+++ b/melektron/inventree-adv-sheet-label.html
@@ -31,11 +31,11 @@
-
+
+{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"melektron"},"dateModified":"2026-02-14T23:57:44+00:00","datePublished":"2026-02-14T23:57:44+00:00","description":"A label printing plugin for InvenTree which provides support for printing labels on off-the-shelf label sheet layouts and adds some more useful features compared to the sheet label plugin included with InvenTree.","headline":"Inventree Adv Sheet Label","mainEntityOfPage":{"@type":"WebPage","@id":"/melektron/inventree-adv-sheet-label"},"url":"/melektron/inventree-adv-sheet-label"}
diff --git a/news/feed.atom b/news/feed.atom
index 9ea2737b..db3fb7e1 100644
--- a/news/feed.atom
+++ b/news/feed.atom
@@ -1,4 +1,4 @@
-Jekyll2026-02-14T20:39:42+00:00/news/feed.atomInvenTree | NewsInvenTree is an open-source inventory management system which provides intuitive parts management and stock control. It is at the center of an ecosystem of addins for EDA tools, API wrapper, deeply integrated plugins and 3rd party tools.1.2.0 Release2026-02-12T00:00:00+00:002026-02-12T00:00:00+00:00/news/2026/02/12/1.2.01.2.0 Release
+Jekyll2026-02-14T23:57:44+00:00/news/feed.atomInvenTree | NewsInvenTree is an open-source inventory management system which provides intuitive parts management and stock control. It is at the center of an ecosystem of addins for EDA tools, API wrapper, deeply integrated plugins and 3rd party tools.1.2.0 Release2026-02-12T00:00:00+00:002026-02-12T00:00:00+00:00/news/2026/02/12/1.2.01.2.0 Release
The InvenTree team is excited to announce the release of version 1.2.0! This update brings a host of new features, improvements, and bug fixes to enhance your experience.
+ 
+ 
