---
author: SchrodingersGat
title: 1.3.0 Release
---

The InvenTree team is excited to announce the release of version 1.3.0. This release includes numerous new features, improvements, and bug fixes.

### Changelog

Major changes are documented in the `CHANGELOG.md` file in the InvenTree repository.

For a full list of changes made in this release, please refer to the [release notes](https://github.com/inventree/InvenTree/releases/tag/1.3.0).

### Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the [InvenTree documentation](https://docs.inventree.org). Note that the particular update procedure may vary depending on your installation method.

## Breaking Changes

The following changes may require updates to custom plugins, API clients, or other integrations with the InvenTree application. Please review these changes carefully before updating to version 1.3.0.

### Supplier Part Model Changes

In [#11303](https://github.com/inventree/InvenTree/pull/11303) we have made a change to the implementation of the supplier part model. While this will not impact most InvenTree users, it may change how custom plugins or external API clients interact with the InvenTree application.

Previously, the *Part* model had a *default_supplier* field, which pointed to a single instance of the *SupplierPart* model. This field has been removed, and instead the *SupplierPart* model has a *primary* field - which is a boolean field indicating whether this supplier part is the primary supplier for the associated part. This change allows for more flexible supplier management.

### Plugin Data Import

In [#11648](https://github.com/inventree/InvenTree/pull/11648) we have added the ability to import custom plugin data from an external data file during the import process. This allows custom plugin data to be migrated across InvenTree instances if required.

### Sqlite Support

In [#11500](https://github.com/inventree/InvenTree/pull/11500) we have made some changes to our support for Sqlite databases. The default implementation now uses a significantly longer connection timeout, and uses write-ahead logging (WAL) mode by default. This should help to reduce the likelihood of database lockouts when using Sqlite, particularly in environments where multiple users may be accessing the database concurrently.

## Security Fixes

There have been a number of security fixes included in this release. We would like to thank the security researchers who have responsibly disclosed these issues to us, and we encourage anyone who discovers a potential security vulnerability in InvenTree to report it to us via our [security policy](https://github.com/inventree/InvenTree/blob/master/SECURITY.md).

### Advisories

The following security advisories have been resolved in this release:

- [GHSA-cx85-vr3q-9x4m](https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m)
- [GHSA-m8j2-vfmq-p6qg](https://github.com/inventree/InvenTree/security/advisories/GHSA-m8j2-vfmq-p6qg)
- [GHSA-rhc5-7c3r-c769](https://github.com/inventree/InvenTree/security/advisories/GHSA-rhc5-7c3r-c769)
- [GHSA-qh5j-c28q-c4rg](https://github.com/inventree/InvenTree/security/advisories/GHSA-qh5j-c28q-c4rg)
- [GHSA-7c3q-vwcv-2vp7](https://github.com/inventree/InvenTree/security/advisories/GHSA-7c3q-vwcv-2vp7)
- [GHSA-r8q5-3595-3jh2](https://github.com/inventree/InvenTree/security/advisories/GHSA-r8q5-3595-3jh2)
- [GHSA-84jh-x777-8pqq](https://github.com/inventree/InvenTree/security/advisories/GHSA-84jh-x777-8pqq)
- [GHSA-m9j7-jw3m-fr22](https://github.com/inventree/InvenTree/security/advisories/GHSA-m9j7-jw3m-fr22)

Refer to the individual advisories for more information about the vulnerabilities that were resolved.

### Pull Requests

In addition to the above advisories, the following pull requests were merged to resolve minor security issues:

- [#11580](https://github.com/inventree/InvenTree/pull/11580) - reduces user scope of the `DataOutput` API endpoint
- [#11602](https://github.com/inventree/InvenTree/pull/11602) - reduces user scope of the `DataImport` API endpoint
- [#11579](https://github.com/inventree/InvenTree/pull/11579) - improves data security around static and media file access
- [#11659](https://github.com/inventree/InvenTree/pull/11659) - adds security banner for superuser accounts

### Project Dependencies

We strive to maintain up-to-date dependencies in the InvenTree project, and we have updated a number of dependencies in this release. 

## New Features

### Order Line Numbering

In [#11692](https://github.com/inventree/InvenTree/pull/11692) we have introduced a "line number" field to external orders, allowing users to specify individual line numbers for each order line. This allows for more flexible ordering and better integration with external systems.

### Generic Parameter Filtering

In [#11383](https://github.com/inventree/InvenTree/pull/11383) we have significantly overhauled the "parameter filtering" system, allowing for more flexible grouping / filtering of parameters.

### Import by Natural Keys

[#11288](https://github.com/inventree/InvenTree/pull/11288) we have added the ability to import data using natural keys, allowing for more intuitive and human-readable data imports. This allows imported data to be mapped to existing database entries using natural keys, rather than relying on internal database IDs. This is particularly useful when migrating data between InvenTree instances, or when importing data from external sources.

### Auto-Allocate Tracked Parts

[#10887](https://github.com/inventree/InvenTree/pull/10887) adds the ability to auto-allocate tracked parts against a build order. This helps to streamline the build allocation process, by providing the auto-allocation feature which has already been available for non-tracked parts.

### Copy Data Cells

[#11406](https://github.com/inventree/InvenTree/pull/11406) introduces the ability to easily copy data directly from table cells. A small but often-requested feature, this allows users to quickly copy data from the InvenTree interface without needing to open individual detail views.

### Zero Quantity BOM

In [#11437](https://github.com/inventree/InvenTree/pull/11437) we have added the ability to create a Bill of Materials (BOM) entry with zero quantity. This allows for more flexible BOM management, particularly in cases where a BOM may be used for reference purposes without needing to specify quantities.

### Plugin Cache Busting

[#11565](https://github.com/inventree/InvenTree/pull/11565) adds a cache-busting mechanism for plugin assets, ensuring that users always receive the latest version of plugin files without needing to manually clear their browser or proxy-server cache. When used in conjunction with the [InvenTree plugin creator](https://github.com/inventree/plugin-creator), this allows plugin developers to easily ensure that users receive the latest version of their plugin assets without needing to worry about caching issues.

### Keep Forms Open

[#11074](https://github.com/inventree/InvenTree/pull/11074) allows certain forms to remain open after submission, allowing users to quickly submit multiple entries without needing to repeatedly open and close the form. This is particularly useful for data entry tasks where multiple similar entries need to be created in quick succession.

### Task Monitoring

[#11527](https://github.com/inventree/InvenTree/pull/11527) introduces the ability to monitor the progress of a single long-running background task via the API. This allows the frontend to provide progress feedback to users when performing long-running operations, and automatically refresh the required data once the task has completed.

## Bug Fixes

As always, we have provided a number of [bug fixes](https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.3.0) with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

## Contributing

### New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

- @tinpham5614 made their first contribution in https://github.com/inventree/InvenTree/pull/11406
- @JustusRijke made their first contribution in https://github.com/inventree/InvenTree/pull/11411
- @jmerro-c3d made their first contribution in https://github.com/inventree/InvenTree/pull/11374
- @tigger2000ttfn made their first contribution in https://github.com/inventree/InvenTree/pull/11484
- @justynbell made their first contribution in https://github.com/inventree/InvenTree/pull/11508
- @Knirps1 made their first contribution in https://github.com/inventree/InvenTree/pull/11512
- @nino-tan-smartee made their first contribution in https://github.com/inventree/InvenTree/pull/11536
- @bbzylstra made their first contribution in https://github.com/inventree/InvenTree/pull/10862
- @amm10090 made their first contribution in https://github.com/inventree/InvenTree/pull/11612
- @spamik made their first contribution in https://github.com/inventree/InvenTree/pull/11074

### Code Contributions

Check out our GitHub page for a list of [outstanding issues](https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22) and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

### Translation

Our [translation efforts](https://crowdin.com/project/inventree) continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our [Crowdin project](https://crowdin.com/project/inventree) and join the community of translators.

### Report Bugs

If you encounter a bug in InvenTree, please report it on our [GitHub issues page](https://github.com/inventree/inventree/issues). Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

### Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

### Financial Support

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

- [GitHub](/fund#github-sponsors)

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.

If your company benefits from InvenTree, please consider a [one time sponsorship](/fund#polar) or a [recurring sponsorship](/fund#polar) to help support the project.