mirror of
https://github.com/inventree/inventree-website.git
synced 2026-11-19 12:57:52 +00:00
1089 lines
110 KiB
XML
1089 lines
110 KiB
XML
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="/blog/feed.atom" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2026-11-19T05:48:57+00:00</updated><id>/blog/feed.atom</id><title type="html">InvenTree</title><subtitle>InvenTree 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.</subtitle><entry><title type="html">1.7.0 Release</title><link href="/blog/2026/11/03/1.7.0" rel="alternate" type="text/html" title="1.7.0 Release" /><published>2026-11-03T00:00:00+00:00</published><updated>2026-11-03T00:00:00+00:00</updated><id>/blog/2026/11/03/1.7.0</id><content type="html" xml:base="/blog/2026/11/03/1.7.0"><![CDATA[<p>InvenTree 1.7.0 has been released! This release includes a critical security fix, a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>Major changes are documented in the <code class="language-plaintext highlighter-rouge">CHANGELOG.md</code> file in the repository. For a full list of changes, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.7.0">release notes</a>.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h2 id="security-fixes">Security Fixes</h2>
|
||
|
||
<p><strong>This release contains a fix for a critical, low-complexity privilege escalation vulnerability, affecting a range of releases since 2025.</strong> Full details, including the associated security advisory, will be published shortly after release — please see our <a href="/blog/2026/11/03/security-release">earlier announcement</a> and watch our <a href="https://github.com/inventree/InvenTree/security/advisories?state=published">security advisories page</a> for the disclosure. If you have not already done so, please update to 1.7.0 as a priority.</p>
|
||
|
||
<p>A number of other security vulnerabilities and hardening improvements are also included in this release.</p>
|
||
|
||
<h3 id="security-advisories">Security Advisories</h3>
|
||
|
||
<p>The following security advisories have been published in relation to this release:</p>
|
||
|
||
<ul>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-wx67-9cjx-8cr8</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-mw93-g6gp-wvqr</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-q3pw-mh42-p63c</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-vv2m-4hv4-5qr8</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-whr7-8gj9-rqvm</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-m4r7-7rrj-gfm2</li>
|
||
</ul>
|
||
|
||
<h3 id="csv-export-formula-injection">CSV Export Formula Injection</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13084">PR #13084</a> sanitizes user-controlled data before it is written into exported CSV files, preventing <a href="https://owasp.org/www-community/attacks/CSV_Injection">CSV injection</a> attacks where a crafted cell value could execute a formula when the export is opened in a spreadsheet application. <a href="https://github.com/inventree/InvenTree/pull/13110">PR #13110</a> is a follow-up fix which relaxes this escaping for legitimate numeric values.</p>
|
||
|
||
<h3 id="report-data-hardening">Report Data Hardening</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13111">PR #13111</a> hardens data access during report generation, excluding sensitive data from the report rendering context and preventing database writes from being triggered as a side effect of generating a report or label.</p>
|
||
|
||
<h3 id="session--token-hardening">Session & Token Hardening</h3>
|
||
|
||
<p>Several related fixes tighten up session and API token handling in this release:</p>
|
||
|
||
<ul>
|
||
<li>Revoking an already-revoked token no longer overwrites the original revocation details (<a href="https://github.com/inventree/InvenTree/pull/13149">PR #13149</a>)</li>
|
||
<li>Token validity checks now also confirm that the owning user account is still active (<a href="https://github.com/inventree/InvenTree/pull/13148">PR #13148</a>)</li>
|
||
<li>Tokens are now masked more securely when displayed, with a fixed lowercase-handling bug and more consistent expiry date checking (<a href="https://github.com/inventree/InvenTree/pull/13155">PR #13155</a>)</li>
|
||
<li>Deleting a <code class="language-plaintext highlighter-rouge">UserSession</code> via the Django admin interface now also logs out the associated user, rather than leaving the session active (<a href="https://github.com/inventree/InvenTree/pull/13145">PR #13145</a>)</li>
|
||
</ul>
|
||
|
||
<h3 id="additional-hardening">Additional Hardening</h3>
|
||
|
||
<p>This release also includes routine security-related dependency updates, including CA certificate updates (<a href="https://github.com/inventree/InvenTree/pull/13057">PR #13057</a>) and a batch of Python dependency security patches (<a href="https://github.com/inventree/InvenTree/pull/13108">PR #13108</a>).</p>
|
||
|
||
<h2 id="breaking-changes">Breaking Changes</h2>
|
||
|
||
<p>While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:</p>
|
||
|
||
<h3 id="pricing-model-refactor">Pricing Model Refactor</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13034">PR #13034</a> moves pricing functionality into a new, dedicated <code class="language-plaintext highlighter-rouge">pricing</code> app, with its own API endpoints and a new “pricing” permission role. Existing users with <code class="language-plaintext highlighter-rouge">part</code> role permissions automatically retain pricing access via a data migration, laying the groundwork for further pricing improvements in future releases.</p>
|
||
|
||
<h3 id="stock-tracking-replaced-by-audit-log">Stock Tracking Replaced by Audit Log</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13101">PR #13101</a> removes the legacy “stock item tracking” model and its associated API endpoints, migrating existing entries into the new global audit log introduced in this same release (see “Changelog / Edit History” under New Features, below). The old stock tracking table only ever captured a subset of model changes; the audit log provides a more complete and consistent record. Any external client applications which read stock tracking data via the old API will need to be updated to use the new <code class="language-plaintext highlighter-rouge">/api/audit/</code> endpoints.</p>
|
||
|
||
<h2 id="new-features">New Features</h2>
|
||
|
||
<h3 id="changelog--edit-history">Changelog / Edit History</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13069">PR #13069</a> introduces a global audit log, built on <a href="https://django-auditlog.readthedocs.io/en/latest/">django-auditlog</a>, which tracks changes made to internal data throughout the system. The log is exposed via new read-only <code class="language-plaintext highlighter-rouge">/api/audit/</code> endpoints, and replaces the previous, more limited stock tracking table (see Breaking Changes, above).</p>
|
||
|
||
<h3 id="token-issuance-notifications">Token Issuance Notifications</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13141">PR #13141</a> notifies a user whenever a new API token is issued against their account — whether via the API, the UI, or by an administrator — and separately warns administrators if no email backend is configured, meaning such security alerts cannot be delivered.</p>
|
||
|
||
<h3 id="plugin-launched-forms--action-context">Plugin-Launched Forms & Action Context</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13174">PR #13174</a> allows plugins to dynamically launch native modal forms without needing to supply their own React components — for example, triggering a built-in API form from a custom primary action. <a href="https://github.com/inventree/InvenTree/pull/13172">PR #13172</a> complements this by passing the current page’s target model and instance ID through to plugin-registered primary actions, giving plugins more context about where they were triggered from.</p>
|
||
|
||
<h3 id="stock-adjustment-barcode-actions">Stock Adjustment Barcode Actions</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13170">PR #13170</a> implements a number of previously-stubbed stock adjustment actions for barcode scanning, rounding out barcode-driven workflows for adjusting stock.</p>
|
||
|
||
<h3 id="default-stock-location-from-part">Default Stock Location from Part</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12916">PR #12916</a> automatically selects the default stock location for a new stock item, if one has been configured against the part being stocked.</p>
|
||
|
||
<h3 id="instance-identity-proof-for-federation">Instance Identity Proof for Federation</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13030">PR #13030</a> adds an optional mechanism for an InvenTree instance to cryptographically prove its identity to a federation participant, without exposing its instance ID directly. A time-limited, replayable proof is computed using HKDF and HMAC, and can be requested as an optional parameter on the root API response — early groundwork for future <a href="https://github.com/inventree/InvenTree/issues/4562">federation</a> work.</p>
|
||
|
||
<h3 id="badge-tooltips">Badge Tooltips</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13074">PR #13074</a> adds explanatory tooltips to the status badges shown on detail pages, making it clearer at a glance what each badge represents.</p>
|
||
|
||
<h2 id="bug-fixes">Bug Fixes</h2>
|
||
|
||
<p>As always, we have provided a number of <a href="https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.7.0">bug fixes</a> with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!</p>
|
||
|
||
<h2 id="contributing">Contributing</h2>
|
||
|
||
<p>InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.</p>
|
||
|
||
<h3 id="new-contributors">New Contributors</h3>
|
||
|
||
<p>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:</p>
|
||
|
||
<ul>
|
||
<li>@Nero7991 made their first contribution in https://github.com/inventree/InvenTree/pull/13100</li>
|
||
<li>@highvoltagescientist-arch made their first contribution in https://github.com/inventree/InvenTree/pull/13122</li>
|
||
</ul>
|
||
|
||
<h3 id="code-contributions">Code Contributions</h3>
|
||
|
||
<p>Check out our GitHub page for a list of <a href="https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22">outstanding issues</a> 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.</p>
|
||
|
||
<h3 id="translation">Translation</h3>
|
||
|
||
<p>Our <a href="https://crowdin.com/project/inventree">translation efforts</a> 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.</p>
|
||
|
||
<p>If you are interested in contributing to the translation efforts, please visit our <a href="https://crowdin.com/project/inventree">Crowdin project</a> and join the community of translators.</p>
|
||
|
||
<h3 id="documentation--technical-writing">Documentation / Technical Writing</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="report-bugs">Report Bugs</h3>
|
||
|
||
<p>If you encounter a bug in InvenTree, please report it on our <a href="https://github.com/inventree/inventree/issues">GitHub issues page</a>. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.</p>
|
||
|
||
<h3 id="financial-contributions">Financial Contributions</h3>
|
||
|
||
<p>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!</p>
|
||
|
||
<p>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!</p>
|
||
|
||
<ul>
|
||
<li><a href="/fund#github-sponsors">GitHub</a></li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>If your company benefits from InvenTree, please consider a <a href="/fund#polar">one time sponsorship</a> or a <a href="/fund#polar">recurring sponsorship</a> to help support the project.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[InvenTree 1.7.0 has been released! This release includes a critical security fix, a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.]]></summary></entry><entry><title type="html">Action required - Upcoming Security Release</title><link href="/blog/2026/11/03/security-release" rel="alternate" type="text/html" title="Action required - Upcoming Security Release" /><published>2026-11-03T00:00:00+00:00</published><updated>2026-11-03T00:00:00+00:00</updated><id>/blog/2026/11/03/security-release</id><content type="html" xml:base="/blog/2026/11/03/security-release"><![CDATA[<p>The InvenTree core development team has received a report of <em>critical security vulnerabilities</em> affecting a large range of releases since 2025. We will release a disclosure and a fixed release as the part of the 1.7.0 release on 2026-11-03 13:00 UTC.<br />
|
||
The vulnerabilities allow known users to privilege escalate within an InvenTree instance. It has a low attack complexity.</p>
|
||
|
||
<h2 id="steps-to-take-now">Steps to take now</h2>
|
||
|
||
<p>We are not aware of active exploitation of this vulnerability, but we recommend that users take the following steps to mitigate risks:</p>
|
||
<ul>
|
||
<li>Do <em>not</em> expose your InvenTree instance to the public internet without hardening steps as laid out in the <a href="https://docs.inventree.org/en/stable/concepts/threat_model/">threat model</a></li>
|
||
<li>Ensure <em>registration is disabled</em> till the release</li>
|
||
<li>Ensure you <em>trust all users registered</em> on your instance, especially those with staff or higher permissions</li>
|
||
</ul>
|
||
|
||
<p>The vulnerabilities have a low complexity and can be expected to be exploited once released. It is important to prepare to update or take your system off the public internet.</p>
|
||
|
||
<h2 id="security-policy">Security Policy</h2>
|
||
|
||
<p>As always with security related themes we remind all users, security researchers, and intrested parties of our <a href="https://inventree.readthedocs.io/en/stable/security/">security policy</a>.</p>
|
||
|
||
<p>If you have discovered a security vulnerability, please report it to us via the channels described in the policy. We take all reports seriously and will work to address any vulnerabilities in a timely manner.</p>
|
||
|
||
<p>We would like to thank the security researchers who reported these and several other vulnerabilities in a responsible manner, and we encourage others to do the same in the future. The reporters will be credited in the disclosure and CVE entry.</p>]]></content><author><name>matmair</name></author><summary type="html"><![CDATA[The InvenTree core development team has received a report of critical security vulnerabilities affecting a large range of releases since 2025. We will release a disclosure and a fixed release as the part of the 1.7.0 release on 2026-11-03 13:00 UTC. The vulnerabilities allow known users to privilege escalate within an InvenTree instance. It has a low attack complexity.]]></summary></entry><entry><title type="html">1.6.0 Release</title><link href="/blog/2026/10/18/1.6.0" rel="alternate" type="text/html" title="1.6.0 Release" /><published>2026-10-18T00:00:00+00:00</published><updated>2026-10-18T00:00:00+00:00</updated><id>/blog/2026/10/18/1.6.0</id><content type="html" xml:base="/blog/2026/10/18/1.6.0"><![CDATA[<p>InvenTree 1.6.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>Major changes are documented in the <code class="language-plaintext highlighter-rouge">CHANGELOG.md</code> file in the repository. For a full list of changes, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.6.0">release notes</a>.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h2 id="breaking-changes">Breaking Changes</h2>
|
||
|
||
<p>While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:</p>
|
||
|
||
<h3 id="notes-refactor">Notes Refactor</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11971">PR #11971</a> is a major refactor of how notes are handled throughout InvenTree. Notes are now stored in a dedicated table (in line with how attachments and parameters are handled), support multiple separate notes per item, and are accessed via the new <code class="language-plaintext highlighter-rouge">/api/note/</code> endpoint rather than a <code class="language-plaintext highlighter-rouge">notes</code> field on individual models. Existing notes data (including embedded images) is automatically migrated into the new table, with markdown content converted to HTML. Any external client applications which read or write the <code class="language-plaintext highlighter-rouge">notes</code> field directly via the API will need to be updated to use the new endpoint.</p>
|
||
|
||
<h3 id="formal-state-transitions">Formal State Transitions</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12507">PR #12507</a> switches build and order status transitions to a more formal finite-state-machine approach. As part of this change, attempting an invalid or repeated state transition now raises a <code class="language-plaintext highlighter-rouge">ValidationError</code> instead of silently failing. Plugins which implement custom transitions should review this change and adjust their usage accordingly to take advantage of the new safeguards.</p>
|
||
|
||
<h3 id="tags-filter-renamed">Tags Filter Renamed</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12672">PR #12672</a> renames the <code class="language-plaintext highlighter-rouge">tags</code> filter — added in 1.4.0 for filtering models by tag — to <code class="language-plaintext highlighter-rouge">tag_name</code>, to avoid a name clash with the <code class="language-plaintext highlighter-rouge">tags</code> field exposed on the same endpoints. Any integration filtering tagged objects via <code class="language-plaintext highlighter-rouge">?tags=</code> must be updated to use <code class="language-plaintext highlighter-rouge">?tag_name=</code> instead.</p>
|
||
|
||
<h3 id="squash-migrations-prior-to-100">Squash Migrations Prior to 1.0.0</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12830">PR #12830</a> squashes all database migrations predating the 1.0.0 release. Any installation still running a pre-1.0.0 version of InvenTree must first update to 1.0.0 before updating to this release.</p>
|
||
|
||
<h3 id="api-token-storage-hardened">API Token Storage Hardened</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12850">PR #12850</a> changes how API tokens are stored, replacing plaintext storage with a peppered HMAC-SHA256 digest, so that gaining read access to the database (for example via a side-channel or IDOR vulnerability) can no longer be used to recover usable API tokens. Newly-issued tokens use a longer “v2” format; existing tokens continue to work, but since the raw token value can no longer be read back from the database, calling <code class="language-plaintext highlighter-rouge">/api/user/me/token/</code> now always reissues (and invalidates) the token rather than returning the existing value.</p>
|
||
|
||
<h2 id="security-fixes">Security Fixes</h2>
|
||
|
||
<p>A number of security vulnerabilities have been fixed in this release.</p>
|
||
|
||
<h3 id="attachment-api-permission-bypass">Attachment API Permission Bypass</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12689">PR #12689</a> fixes a flaw in the Attachment API where user role permissions were not checked against the owning model, allowing any authenticated user to enumerate and download attachments they should not have had access to. The API now checks the requesting user’s view permissions and returns <code class="language-plaintext highlighter-rouge">PermissionDenied</code> where appropriate.</p>
|
||
|
||
<h3 id="metadata-endpoint-information-disclosure">Metadata Endpoint Information Disclosure</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12771">PR #12771</a> restricts the generic metadata API endpoints to a fixed set of safe lookup fields, closing a path where arbitrary field names could be used to perform unintended database queries and recover data outside the intended scope.</p>
|
||
|
||
<h3 id="data-import-session-retargeting">Data Import Session Retargeting</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12809">PR #12809</a> prevents the target model type of a data import session from being changed after the import has started, closing a gap where a user could bypass the authorization check performed against the original target model.</p>
|
||
|
||
<h3 id="stock-locate-permission-check">Stock Locate Permission Check</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13000">PR #13000</a> adds a missing permission check to the “locate stock” plugin action endpoint, which previously allowed any authenticated user to trigger the action and enumerate stock regardless of their assigned role.</p>
|
||
|
||
<h3 id="additional-hardening">Additional Hardening</h3>
|
||
|
||
<p>A number of smaller permission and hardening fixes are also included in this release:</p>
|
||
|
||
<ul>
|
||
<li>Calendar <code class="language-plaintext highlighter-rouge">.ics</code> feeds (<a href="https://github.com/inventree/InvenTree/pull/12764">PR #12764</a>) and the <code class="language-plaintext highlighter-rouge">SelectionList</code> API (<a href="https://github.com/inventree/InvenTree/pull/12763">PR #12763</a>) now correctly check user permissions</li>
|
||
<li>Users may only edit their own profile, and may only access notes or parameters against models they are scoped to (<a href="https://github.com/inventree/InvenTree/pull/12766">PR #12766</a>)</li>
|
||
<li>The <code class="language-plaintext highlighter-rouge">/api/user/me/</code> endpoint can no longer be used to delete your own account (<a href="https://github.com/inventree/InvenTree/pull/12770">PR #12770</a>)</li>
|
||
<li>The <code class="language-plaintext highlighter-rouge">MachineSettingList</code> endpoint now requires the admin role, and barcode generation is permission-checked (<a href="https://github.com/inventree/InvenTree/pull/12886">PR #12886</a>)</li>
|
||
<li>Potentially dangerous tags are stripped from uploaded SVG files (<a href="https://github.com/inventree/InvenTree/pull/12687">PR #12687</a>)</li>
|
||
<li>User-facing input is sanitized more robustly before being rendered into WeasyPrint reports (<a href="https://github.com/inventree/InvenTree/pull/12997">PR #12997</a>)</li>
|
||
<li>New secret keys are now generated using Django’s own helper rather than a custom implementation (<a href="https://github.com/inventree/InvenTree/pull/12999">PR #12999</a>)</li>
|
||
<li>Installer scripts have been hardened against a number of possible injection points (<a href="https://github.com/inventree/InvenTree/pull/12819">PR #12819</a>)</li>
|
||
<li>InvenTree now warns administrators if an unsafe wildcard CORS configuration is detected (<a href="https://github.com/inventree/InvenTree/pull/12773">PR #12773</a>)</li>
|
||
</ul>
|
||
|
||
<h3 id="security-advisories">Security Advisories</h3>
|
||
|
||
<p>The following security advisories have been published in relation to this release:</p>
|
||
|
||
<ul>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-9mm7-c3mq-6c99</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-hv74-9q5w-p8v3</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-p9q2-5w65-82g5</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-q6vh-g752-53g8</li>
|
||
</ul>
|
||
|
||
<p>For more information, please refer to our <a href="https://github.com/inventree/InvenTree/security/advisories?state=published">security advisories page</a></p>
|
||
|
||
<h2 id="database-changes">Database Changes</h2>
|
||
|
||
<p>This release includes a number of changes to the underlying database schema and data validation. As always, a backup of your database is recommended before performing the update.</p>
|
||
|
||
<h3 id="legacy-session-table-cleanup">Legacy Session Table Cleanup</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12675">PR #12675</a> removes a legacy database table left behind on older installations that predate the removal of the <code class="language-plaintext highlighter-rouge">django-user-sessions</code> package, fixing a foreign-key error that could occur when deleting a user. <a href="https://github.com/inventree/InvenTree/pull/12697">PR #12697</a> is a follow-up fix ensuring this migration also runs correctly on MySQL-backed installations.</p>
|
||
|
||
<h3 id="notes-migration-fix-for-mysql">Notes Migration Fix for MySQL</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12808">PR #12808</a> fixes the data migration introduced by the notes refactor (<a href="https://github.com/inventree/InvenTree/pull/11971">PR #11971</a>), which did not run correctly on MySQL due to differences in how that backend returns rows created via <code class="language-plaintext highlighter-rouge">bulk_create</code>. Migration regression testing is now performed against all supported database backends to catch this class of issue earlier.</p>
|
||
|
||
<h3 id="shipment--address-contact-fields">Shipment & Address Contact Fields</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13016">PR #13016</a> adds a <code class="language-plaintext highlighter-rouge">contact</code> field to the <code class="language-plaintext highlighter-rouge">SalesOrderShipment</code> model, and <code class="language-plaintext highlighter-rouge">phone_number</code> and <code class="language-plaintext highlighter-rouge">email</code> fields to the <code class="language-plaintext highlighter-rouge">Address</code> model, allowing more complete contact details to be recorded against shipments and addresses.</p>
|
||
|
||
<h2 id="new-features">New Features</h2>
|
||
|
||
<h3 id="internal-companies--purchase-order-delivery-address">Internal Companies & Purchase Order Delivery Address</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13017">PR #13017</a> introduces the concept of an “internal” company — a flag on the <code class="language-plaintext highlighter-rouge">Company</code> model used to represent your own organization, configurable via the new <code class="language-plaintext highlighter-rouge">INVENTREE_DEFAULT_INTERNAL_COMPANY</code> setting and exposed to report templates as <code class="language-plaintext highlighter-rouge">internal_company</code>. Building on this, <a href="https://github.com/inventree/InvenTree/pull/9768">PR #9768</a> adds a dedicated delivery address field to purchase orders, which must reference an internal company.</p>
|
||
|
||
<h3 id="docker-compose-health-checks">Docker Compose Health Checks</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12124">PR #12124</a> adds health checks to each container in the Docker Compose stack, with dependent containers now waiting for their dependencies to report healthy before starting (for example, the worker waits on the server, and the server waits on the database and cache).</p>
|
||
|
||
<h3 id="cut-to-length-bom-items">Cut-to-Length BOM Items</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12422">PR #12422</a> adds <code class="language-plaintext highlighter-rouge">piece_count</code> and <code class="language-plaintext highlighter-rouge">piece_size</code> fields to BOM items, for assemblies that require a number of discrete pieces cut from continuous stock such as cable, tubing, or structural profiles. When a piece size is specified, the total required quantity is calculated automatically, while still preserving the per-piece information needed for purchasing and production.</p>
|
||
|
||
<h3 id="persistent-previousnext-navigation">Persistent Previous/Next Navigation</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12585">PR #12585</a> improves detail-page navigation from filtered tables: Previous and Next controls now remember the filtered result set via the URL, and a subtle “x of y” indicator shows your position within it, making it much easier to step through a filtered list of parts, orders, or other items.</p>
|
||
|
||
<h3 id="bulk-edit-return-order-line-items">Bulk-Edit Return Order Line Items</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12635">PR #12635</a> allows the outcome of multiple return order line items to be changed at once, rather than editing each line individually.</p>
|
||
|
||
<h3 id="expanded-identity-federation-scim-oidc--saml">Expanded Identity Federation: SCIM, OIDC & SAML</h3>
|
||
|
||
<p>This release brings together a larger identity federation initiative. <a href="https://github.com/inventree/InvenTree/pull/12713">PR #12713</a> adds SCIM 2.0 support for provisioning users and groups from an external identity provider. <a href="https://github.com/inventree/InvenTree/pull/12731">PR #12731</a> switches the built-in OIDC/OAuth2 provider on by default (previously available but opt-in), and consolidates the related settings into the Admin Center. <a href="https://github.com/inventree/InvenTree/pull/12799">PR #12799</a> rounds this out with a guided SAML configuration helper in the frontend, making it easier to connect InvenTree to a SAML-based identity provider.</p>
|
||
|
||
<h3 id="plugin-well-known-urls">Plugin Well-Known URLs</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12698">PR #12698</a> adds a mixin allowing plugins to register entries under the <code class="language-plaintext highlighter-rouge">.well-known</code> path, useful for authentication discovery and other system integrations.</p>
|
||
|
||
<h3 id="faster-bulk-data-import">Faster Bulk Data Import</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12792">PR #12792</a> adds an opt-in bulk-create mode to the <code class="language-plaintext highlighter-rouge">import-records</code> management task, dramatically speeding up large dataset imports (in testing, a 1.2 million row dataset dropped from around 16 minutes to roughly 1 minute).</p>
|
||
|
||
<h3 id="stock-location-owner-field-in-the-ui">Stock Location Owner Field in the UI</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12826">PR #12826</a> exposes the Owner field on the stock location create/edit form, restoring parity with the stock item form and matching documented (but previously missing) UI behavior.</p>
|
||
|
||
<h3 id="rotated-table-headers">Rotated Table Headers</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12837">PR #12837</a> adds a user setting which renders long table column titles vertically rather than horizontally, saving significant horizontal space in parameter-heavy tables. The option is off by default.</p>
|
||
|
||
<h3 id="hide-unused-order-types-from-the-ui">Hide Unused Order Types from the UI</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12842">PR #12842</a> adds administrator toggles to fully hide Sales Order, Purchase Order, or Build Order functionality from the interface, for instances that don’t make use of them.</p>
|
||
|
||
<h3 id="plugin-custom-pages">Plugin Custom Pages</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12900">PR #12900</a> adds a new <code class="language-plaintext highlighter-rouge">route</code> UI feature type, allowing plugins to register entirely new frontend pages (served under <code class="language-plaintext highlighter-rouge">/web/plugin/<plugin>/...</code>) in addition to the existing panel and dashboard widget integration points.</p>
|
||
|
||
<h3 id="default-receive-location">Default Receive Location</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12911">PR #12911</a> adds a global setting to configure a default stock location for receiving items against purchase orders.</p>
|
||
|
||
<h3 id="global-batch-code-for-purchase-order-receipt">Global Batch Code for Purchase Order Receipt</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12912">PR #12912</a> adds a batch code that can be set once when receiving a purchase order and applied across all received items, with the option to override it on individual line items.</p>
|
||
|
||
<h3 id="background-task-timeouts--single-shot-mode">Background Task Timeouts & Single-Shot Mode</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12913">PR #12913</a> adds per-task timeout configuration and an optional single-shot mode (disabling automatic retry on failure) for background tasks, giving more control over long-running or non-idempotent jobs.</p>
|
||
|
||
<h3 id="per-user-notification-localization">Per-User Notification Localization</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12944">PR #12944</a> renders notification emails and in-app messages in each recipient’s own language preference, rather than the server process’s default locale, with efficient per-locale batching for email delivery.</p>
|
||
|
||
<h3 id="nested-bom-display">Nested BOM Display</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12952">PR #12952</a> implements a true nested BOM view, replacing the previous reduced-dataset subassembly table and displaying the total quantity of each sub-item — including across multiplier chains of nested subassemblies.</p>
|
||
|
||
<h3 id="pinned-resizable-navigation-sidebar">Pinned, Resizable Navigation Sidebar</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12974">PR #12974</a> adds an optional side-by-side navigation tree that stays pinned alongside the main content. It can be resized via a splitter (collapsing automatically when dragged small), and toggled on from user settings or a pin button in the header.</p>
|
||
|
||
<h3 id="first-time-user-guide">First-Time User Guide</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12978">PR #12978</a> adds a short, dismissible onboarding tour for new users, along with backend data structures to support further guided tours in future releases.</p>
|
||
|
||
<h3 id="plugin-reload-cycle-detection">Plugin Reload Cycle Detection</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/13007">PR #13007</a> improves automatic plugin reload handling and documents its limitations — binary plugins and changed dependencies cannot be hot-reloaded. The system now detects and reports plugin reload cycles instead of looping indefinitely.</p>
|
||
|
||
<h2 id="bug-fixes">Bug Fixes</h2>
|
||
|
||
<p>As always, we have provided a number of <a href="https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.6.0">bug fixes</a> with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!</p>
|
||
|
||
<h2 id="contributing">Contributing</h2>
|
||
|
||
<p>InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.</p>
|
||
|
||
<h3 id="new-contributors">New Contributors</h3>
|
||
|
||
<p>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:</p>
|
||
|
||
<ul>
|
||
<li>@FurinaDog made their first contribution in https://github.com/inventree/InvenTree/pull/12616</li>
|
||
<li>@ribsey made their first contribution in https://github.com/inventree/InvenTree/pull/12550</li>
|
||
<li>@amanjain57-gif made their first contribution in https://github.com/inventree/InvenTree/pull/12422</li>
|
||
<li>@Alonso-Lopez-1 made their first contribution in https://github.com/inventree/InvenTree/pull/12286</li>
|
||
<li>@Jr-kenny made their first contribution in https://github.com/inventree/InvenTree/pull/12585</li>
|
||
<li>@psxjt5 made their first contribution in https://github.com/inventree/InvenTree/pull/12703</li>
|
||
<li>@wyyd-yxc made their first contribution in https://github.com/inventree/InvenTree/pull/12826</li>
|
||
<li>@lizerui1608-dev made their first contribution in https://github.com/inventree/InvenTree/pull/12888</li>
|
||
<li>@fquinto made their first contribution in https://github.com/inventree/InvenTree/pull/12926</li>
|
||
<li>@BI7KHI made their first contribution in https://github.com/inventree/InvenTree/pull/12784</li>
|
||
<li>@xyz-is-best made their first contribution in https://github.com/inventree/InvenTree/pull/12944</li>
|
||
<li>@maxgr0 made their first contribution in https://github.com/inventree/InvenTree/pull/12973</li>
|
||
<li>@gotoUSA made their first contribution in https://github.com/inventree/InvenTree/pull/12990</li>
|
||
<li>@tijsmoree made their first contribution in https://github.com/inventree/InvenTree/pull/12966</li>
|
||
</ul>
|
||
|
||
<h3 id="code-contributions">Code Contributions</h3>
|
||
|
||
<p>Check out our GitHub page for a list of <a href="https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22">outstanding issues</a> 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.</p>
|
||
|
||
<h3 id="translation">Translation</h3>
|
||
|
||
<p>Our <a href="https://crowdin.com/project/inventree">translation efforts</a> 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.</p>
|
||
|
||
<p>If you are interested in contributing to the translation efforts, please visit our <a href="https://crowdin.com/project/inventree">Crowdin project</a> and join the community of translators.</p>
|
||
|
||
<h3 id="documentation--technical-writing">Documentation / Technical Writing</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="report-bugs">Report Bugs</h3>
|
||
|
||
<p>If you encounter a bug in InvenTree, please report it on our <a href="https://github.com/inventree/inventree/issues">GitHub issues page</a>. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.</p>
|
||
|
||
<h3 id="financial-contributions">Financial Contributions</h3>
|
||
|
||
<p>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!</p>
|
||
|
||
<p>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!</p>
|
||
|
||
<ul>
|
||
<li><a href="/fund#github-sponsors">GitHub</a></li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>If your company benefits from InvenTree, please consider a <a href="/fund#polar">one time sponsorship</a> or a <a href="/fund#polar">recurring sponsorship</a> to help support the project.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[InvenTree 1.6.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.]]></summary></entry><entry><title type="html">InvenTree MCP Plugin</title><link href="/blog/2026/09/17/inventree-mcp" rel="alternate" type="text/html" title="InvenTree MCP Plugin" /><published>2026-09-17T00:00:00+00:00</published><updated>2026-09-17T00:00:00+00:00</updated><id>/blog/2026/09/17/inventree-mcp</id><content type="html" xml:base="/blog/2026/09/17/inventree-mcp"><![CDATA[<p>The InvenTree development team is excited to introduce <a href="https://github.com/inventree/inventree-mcp">InvenTreeMCP</a>, a new plugin which exposes your InvenTree inventory data to AI agents and other MCP-aware applications via the <a href="https://modelcontextprotocol.io">Model Context Protocol</a> (MCP).</p>
|
||
|
||
<h3 id="what-is-it-for">What is it for?</h3>
|
||
|
||
<p>MCP is an open standard which allows AI assistants - such as Claude - to interact with external tools and data sources in a structured way. InvenTreeMCP implements an MCP server as an InvenTree plugin, allowing any MCP client to query your InvenTree instance directly, over a Streamable HTTP endpoint.</p>
|
||
|
||
<p>This means you can ask an AI assistant questions about your inventory - stock levels, open orders, BOM structures, and more - and have it query your live InvenTree data to provide an answer, without needing to write any custom integration code.</p>
|
||
|
||
<p>Under the hood, InvenTreeMCP is implemented as a thin layer on top of the existing InvenTree API. Every request made by an MCP client passes through the same permission checks and filtering as a normal API call, so users only ever see the data they are already allowed to access.</p>
|
||
|
||
<h3 id="what-tools-does-it-expose">What tools does it expose?</h3>
|
||
|
||
<p>InvenTreeMCP currently exposes read access to the core InvenTree data model, including:</p>
|
||
|
||
<ul>
|
||
<li>Parts and part categories</li>
|
||
<li>Stock items and stock locations</li>
|
||
<li>Purchase, sales, return and build orders (and their line items)</li>
|
||
<li>Companies and contacts</li>
|
||
<li>Manufacturer and supplier parts</li>
|
||
<li>Bill of materials (BOM) items</li>
|
||
<li>Attachments and parameters</li>
|
||
<li>Stock tracking history and test results</li>
|
||
<li>Project codes</li>
|
||
</ul>
|
||
|
||
<p>Tool schemas and available filters are generated automatically from InvenTree’s existing API serializers, so the tools exposed to MCP clients stay in sync with the underlying data model as InvenTree evolves.</p>
|
||
|
||
<h3 id="how-can-it-be-used">How can it be used?</h3>
|
||
|
||
<p>InvenTreeMCP can be installed like any other InvenTree plugin:</p>
|
||
|
||
<ol>
|
||
<li>Install the plugin, e.g. via pip: <code class="language-plaintext highlighter-rouge">pip install inventree-mcp</code></li>
|
||
<li>Enable the plugin under <em>Admin > Plugins</em></li>
|
||
<li>Generate an API token in InvenTree for your MCP client to use</li>
|
||
</ol>
|
||
|
||
<p>Once installed and enabled, the MCP server is available at a URL such as <code class="language-plaintext highlighter-rouge">https://<your-inventree-server>/plugin/inventree-mcp/mcp/</code>. Most MCP clients which support remote (Streamable HTTP) servers can be pointed directly at this endpoint, authenticating with an InvenTree API token, e.g.:</p>
|
||
|
||
<div class="language-json highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{</span><span class="w">
|
||
</span><span class="nl">"mcpServers"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
|
||
</span><span class="nl">"inventree"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
|
||
</span><span class="nl">"url"</span><span class="p">:</span><span class="w"> </span><span class="s2">"https://<your-inventree-server>/plugin/inventree-mcp/mcp/"</span><span class="p">,</span><span class="w">
|
||
</span><span class="nl">"headers"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
|
||
</span><span class="nl">"Authorization"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Token <your-api-token>"</span><span class="w">
|
||
</span><span class="p">}</span><span class="w">
|
||
</span><span class="p">}</span><span class="w">
|
||
</span><span class="p">}</span><span class="w">
|
||
</span><span class="p">}</span><span class="w">
|
||
</span></code></pre></div></div>
|
||
|
||
<p>For clients which only support local (stdio) MCP servers, the <a href="https://github.com/geelen/mcp-remote"><code class="language-plaintext highlighter-rouge">mcp-remote</code></a> bridge can be used to connect to the same endpoint.</p>
|
||
|
||
<p>In addition to API tokens, the plugin also supports authentication via username/password, or OAuth2 bearer tokens with optional scope restrictions - useful if you want to issue narrowly-scoped credentials to a particular agent.</p>
|
||
|
||
<p>By default, the plugin runs in <em>read only</em> mode, which blocks any write operations regardless of the permissions of the authenticating user. This is a sensible default while you get a feel for how your AI tooling of choice interacts with your InvenTree data.</p>
|
||
|
||
<h3 id="feedback-welcome">Feedback Welcome</h3>
|
||
|
||
<p>InvenTreeMCP is a brand new plugin, and this is very much a first step towards richer AI integration with InvenTree. We would love to hear how you’re using it, and what’s working (or not working) for your setup.</p>
|
||
|
||
<p>If you run into any bugs, or have trouble with installation or configuration, please <a href="https://github.com/inventree/inventree-mcp/issues">open an issue</a> on the GitHub repository.</p>
|
||
|
||
<p>If there are additional tools or data types you’d like to see exposed via MCP, we’d also love to hear your suggestions - feel free to raise a feature request on the same <a href="https://github.com/inventree/inventree-mcp/issues">issue tracker</a>.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[The InvenTree development team is excited to introduce InvenTreeMCP, a new plugin which exposes your InvenTree inventory data to AI agents and other MCP-aware applications via the Model Context Protocol (MCP).]]></summary></entry><entry><title type="html">Action required - Package Repository Change</title><link href="/blog/2026/09/09/package-repo" rel="alternate" type="text/html" title="Action required - Package Repository Change" /><published>2026-09-09T00:00:00+00:00</published><updated>2026-09-09T00:00:00+00:00</updated><id>/blog/2026/09/09/package-repo</id><content type="html" xml:base="/blog/2026/09/09/package-repo"><![CDATA[<p>Due to changes to the package publishing platform, packager.io, all users of the package-based installer (most often installed through the 1-line install script) must manually update their package repository configuration to continue receiving updates.</p>
|
||
|
||
<p>The following Bash commands will ensure that you continue receiving updates from the new package repository configuration. The update procedure, package structure and general commands are unchanged.</p>
|
||
|
||
<h2 id="upgrade-instructions">Upgrade Instructions</h2>
|
||
|
||
<h3 id="command-for-ubuntu-2604">Command for Ubuntu 26.04</h3>
|
||
|
||
<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg"</span> <span class="nt">-o</span> /usr/share/keyrings/InvenTree.gpg
|
||
<span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/inventree/InvenTree/stable/installer/ubuntu/26.04.list"</span> <span class="nt">-o</span> /etc/apt/sources.list.d/InvenTree.list
|
||
<span class="nb">sudo </span>apt update
|
||
<span class="nb">sudo </span>apt <span class="nb">install</span> <span class="nt">-y</span> inventree
|
||
</code></pre></div></div>
|
||
|
||
<h3 id="command-for-ubuntu-2404">Command for Ubuntu 24.04</h3>
|
||
|
||
<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg"</span> <span class="nt">-o</span> /usr/share/keyrings/InvenTree.gpg
|
||
<span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/inventree/InvenTree/stable/installer/ubuntu/24.04.list"</span> <span class="nt">-o</span> /etc/apt/sources.list.d/InvenTree.list
|
||
<span class="nb">sudo </span>apt update
|
||
<span class="nb">sudo </span>apt <span class="nb">install</span> <span class="nt">-y</span> inventree
|
||
</code></pre></div></div>
|
||
|
||
<h3 id="command-for-debian-13">Command for Debian 13</h3>
|
||
<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg"</span> <span class="nt">-o</span> /usr/share/keyrings/InvenTree.gpg
|
||
<span class="nb">sudo </span>curl <span class="nt">-fsSL</span> <span class="s2">"https://go.packager.io/srv/inventree/InvenTree/beta/installer/debian/13.list"</span> <span class="nt">-o</span> /etc/apt/sources.list.d/InvenTree.list
|
||
<span class="nb">sudo </span>apt update
|
||
<span class="nb">sudo </span>apt <span class="nb">install</span> <span class="nt">-y</span> inventree
|
||
</code></pre></div></div>
|
||
|
||
<h2 id="supported-os-versions---you-might-need-to-upgrade">Supported OS versions - you might need to upgrade</h2>
|
||
|
||
<p>We are phasing out versions of Ubuntu and Debian that are at, or approaching, end of support, particularly as Python 3.11 has only one year until EOL.</p>
|
||
|
||
<p>If you are on Ubuntu 20.04 (LTS) - which many of the old Docker droplet deployments were on - it is strongly recommended to update to 26.04 (LTS) to continue receiving updates. This will likely also require you to update your postgres version to at least 14, recommended is 17 or 18. Note that postgres updates should be done in single version steps (13 -> 14 -> 15 -> 16 -> 17 -> 18) or with <a href="https://www.postgresql.org/docs/18/pgupgrade.html">pgupgrade</a>.<br />
|
||
The volunteer InvenTree core team does not have the resources to assist with individual upgrades.</p>
|
||
|
||
<h2 id="additional-notes-on-os-version-selections">Additional Notes on OS version selections</h2>
|
||
|
||
<p>As of InvenTree version 1.5.3, the supported versions are Debian 13 and Ubuntu 24.04 / 26.04 LTS. This is mainly because Bookworm is the only supported Debian release <a href="https://wiki.debian.org/Python#Supported_Python_Versions">shipping Python 3.11</a> (as does <a href="https://ubuntu.com/developers/docs/reference/availability/python/">Ubuntu 22.04</a>).</p>
|
||
|
||
<p>As Python 3.11 has received only security updates since 2024 and will reach EOL in October 2027, the libraries on which we depend have increasingly announced that they will soon end support for it. Although most still support it, this is likely to change. Therefore, we are raising the minimum versions in advance so that we are not caught off guard by dependency issues that require urgent releases.</p>
|
||
|
||
<p>Python 3.12 also has <a href="https://docs.python.org/3.12/whatsnew/3.12.html">some nice QoL features</a> that developers using Python 3.14 (myself included) can forget are relatively new. It also drops distutils and a few importlib functions. Raising the minimum versions allows us to drop shims and use these newer features.</p>
|
||
|
||
<h2 id="acknowledgements">Acknowledgements</h2>
|
||
|
||
<p>We are very thankful to Cyril Rohr for packager.io and the support provided on various issues and questions throughout the years. We are not switching away from his solutions, but using the newer version, go.packager.io, as the old one is being sunset in the near future.</p>]]></content><author><name>matmair</name></author><summary type="html"><![CDATA[Due to changes to the package publishing platform, packager.io, all users of the package-based installer (most often installed through the 1-line install script) must manually update their package repository configuration to continue receiving updates.]]></summary></entry><entry><title type="html">1.5.0 Release</title><link href="/blog/2026/08/09/1.5.0" rel="alternate" type="text/html" title="1.5.0 Release" /><published>2026-08-09T00:00:00+00:00</published><updated>2026-08-09T00:00:00+00:00</updated><id>/blog/2026/08/09/1.5.0</id><content type="html" xml:base="/blog/2026/08/09/1.5.0"><![CDATA[<p>InvenTree 1.5.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>Major changes are documented in the <code class="language-plaintext highlighter-rouge">CHANGELOG.md</code> file in the repository. For a full list of changes, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.5.0">release notes</a>.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h2 id="breaking-changes">Breaking Changes</h2>
|
||
|
||
<p>While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:</p>
|
||
|
||
<h3 id="api-throttling-enabled-by-default">API Throttling Enabled by Default</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11951">PR #11951</a> enables API request throttling by default, providing a first line of defense against trivial denial-of-service abuse of API endpoints. The default limits are intentionally generous so as to minimize impact on most instances, but administrators of smaller or resource-constrained instances should review the new throttling configuration.</p>
|
||
|
||
<h3 id="bump-minimum-python-version">Bump Minimum Python Version</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12223">PR #12223</a> raises the minimum supported Python version to 3.12, and drops pre-built packages for Debian 11 and Ubuntu 22.04. Users running InvenTree on an older Python version, or on one of these older distributions, will need to upgrade their environment before installing this release.</p>
|
||
|
||
<h3 id="table-field-refactor">Table Field Refactor</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12274">PR #12274</a> rewrites how “table” fields are rendered in UI forms, fixing a number of performance issues where rows were needlessly re-created on every update. As part of this refactor, each row now requires a unique ID value. Any custom plugins that use “table” field types in UI forms will need to be adjusted to match the new configuration.</p>
|
||
|
||
<h3 id="refactor-api-for-duplicating-objects">Refactor API for Duplicating Objects</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12294">PR #12294</a> consolidates the various object-duplication endpoints behind a single <code class="language-plaintext highlighter-rouge">DuplicateOptionsSerializer</code>, and extends duplication support to additional models (including the ability to copy notes). Integrations which rely on the previous per-model duplication endpoints should be reviewed against the new consolidated API.</p>
|
||
|
||
<h3 id="adjust-default-behavior-of-migrate-command">Adjust Default Behavior of “migrate” Command</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12320">PR #12320</a> changes the default behavior of the <code class="language-plaintext highlighter-rouge">invoke update</code> command so that it no longer automatically generates new migration files when the database schema has changed. This prevents installations from ending up with out-of-line migration files that were not committed to the repository. Developers who rely on migrations being auto-generated during update will need to generate them explicitly.</p>
|
||
|
||
<h3 id="remove-dead-pricing-code-on-part-model">Remove Dead Pricing Code on Part Model</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12357">PR #12357</a> removes a number of legacy pricing methods from the <code class="language-plaintext highlighter-rouge">Part</code> model, in preparation for a larger pricing refactor. While this does not affect any internally called code, any plugins relying on these legacy methods being available will need to be adjusted.</p>
|
||
|
||
<h3 id="remove-mptt-mixin-from-stockitem-model">Remove MPTT Mixin from StockItem Model</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12360">PR #12360</a> removes the MPTT tree mixin from the <code class="language-plaintext highlighter-rouge">StockItem</code> model. The model never made real use of MPTT’s tree features, but paid the cost of expensive tree rebuilds and fragile concurrency locking on every bulk stock operation. Removing it reduces database load and eliminates a class of concurrency issues during bulk stock actions. External clients should note that the tree-related fields previously exposed on <code class="language-plaintext highlighter-rouge">StockItem</code> are no longer available via the API.</p>
|
||
|
||
<h3 id="optional-field-permissions">Optional Field Permissions</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12529">PR #12529</a> fixes a permission gap where “optional fields” exposing cross-model relations were returned regardless of whether the requesting user had permission to view the related model. These optional fields are now excluded from API responses if the user lacks view permission on the associated model, so integrations that depended on always receiving these fields may need to handle their absence.</p>
|
||
|
||
<h2 id="security-fixes">Security Fixes</h2>
|
||
|
||
<p>A number of security vulnerabilities have been fixed in this release.</p>
|
||
|
||
<h3 id="fix-permissions-for-group-and-ruleset-endpoints">Fix Permissions for Group and RuleSet Endpoints</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12563">PR #12563</a> tightens access to the group and <code class="language-plaintext highlighter-rouge">RuleSet</code> API endpoints, which previously only checked the <code class="language-plaintext highlighter-rouge">is_staff</code> flag. These endpoints now also require the user to hold the <code class="language-plaintext highlighter-rouge">StaffRole</code> permission, closing a gap that allowed staff users without the appropriate role to view or modify permission rulesets.</p>
|
||
|
||
<h3 id="additional-ssrf-protections">Additional SSRF Protections</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12595">PR #12595</a> further tightens the protections around fetching data from external URLs, reducing the risk of server-side request forgery (SSRF) when InvenTree makes outgoing requests on a user’s behalf.</p>
|
||
|
||
<h2 id="database-changes">Database Changes</h2>
|
||
|
||
<p>This release includes a number of changes to the underlying database schema and data validation. As always, a backup of your database is recommended before performing the update.</p>
|
||
|
||
<h3 id="fix-for-uuid-fields">Fix for UUID Fields</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12301">PR #12301</a> introduces a custom UUID field to work around a Django 5.0 change to <code class="language-plaintext highlighter-rouge">UUIDField</code> handling on MariaDB. This resolves migration issues that could occur when updating existing UUID columns on MariaDB-backed installations.</p>
|
||
|
||
<h3 id="fix-currency-choices-for-partpricing-model">Fix Currency Choices for PartPricing Model</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12336">PR #12336</a> removes the dynamically-generated currency choices from the <code class="language-plaintext highlighter-rouge">PartPricing</code> model definition, moving that validation into the API serializer instead, along with a dedicated validator to ensure only supported currency codes can be assigned.</p>
|
||
|
||
<h3 id="unique-parameters">Unique Parameters</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12388">PR #12388</a> adds uniqueness validation options to the <code class="language-plaintext highlighter-rouge">ParameterTemplate</code> model, allowing administrators to enforce that values for a given parameter template must be unique across parts.</p>
|
||
|
||
<h3 id="data-import-fix">Data Import Fix</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12568">PR #12568</a> fixes an encoding issue that could occur when importing date values from Excel files during the data import process.</p>
|
||
|
||
<h2 id="new-features">New Features</h2>
|
||
|
||
<h3 id="tree-select-in-form-fields">Tree Select in Form Fields</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12217">PR #12217</a> adds a hierarchical “tree select” control for choosing stock locations and part categories in UI forms, making it much easier to navigate deeply nested location and category structures when filling out a form.</p>
|
||
|
||
<h3 id="snippet-editor">Snippet Editor</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12299">PR #12299</a> adds a dedicated UI for managing report assets and snippets, making it easier to create and maintain reusable template fragments for report and label generation.</p>
|
||
|
||
<h3 id="form-submission-shortcut">Form Submission Shortcut</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12328">PR #12328</a> adds a keyboard shortcut (<code class="language-plaintext highlighter-rouge">Ctrl</code> + <code class="language-plaintext highlighter-rouge">Enter</code>) to submit the currently open form, speeding up repetitive data-entry workflows.</p>
|
||
|
||
<h3 id="break-apart-assemblies">Break Apart Assemblies</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12310">PR #12310</a> introduces a long-requested “disassembly” feature, allowing an assembly to be broken apart back into its constituent BOM items. The feature is supported for untracked, tracked (serialized), and mixed assemblies, and preserves the originating purchase order and build order history on the resulting stock items.</p>
|
||
|
||
<h3 id="preview-drawer">Preview Drawer</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12117">PR #12117</a> adds a global “preview drawer” which provides a quick-view of a part, stock item, order, or other object without navigating away from the current page. Preview rendering is available for all core models, and is also exposed to plugins so they can supply their own preview content.</p>
|
||
|
||
<h2 id="bug-fixes">Bug Fixes</h2>
|
||
|
||
<p>As always, we have provided a number of <a href="https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.5.0">bug fixes</a> with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!</p>
|
||
|
||
<h2 id="contributing">Contributing</h2>
|
||
|
||
<p>InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.</p>
|
||
|
||
<h3 id="new-contributors">New Contributors</h3>
|
||
|
||
<p>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:</p>
|
||
|
||
<ul>
|
||
<li>@suzunn made their first contribution in https://github.com/inventree/InvenTree/pull/12215</li>
|
||
<li>@ledvinap made their first contribution in https://github.com/inventree/InvenTree/pull/12332</li>
|
||
<li>@br413 made their first contribution in https://github.com/inventree/InvenTree/pull/12413</li>
|
||
<li>@Leopoldius made their first contribution in https://github.com/inventree/InvenTree/pull/12424</li>
|
||
<li>@aamirasmal15 made their first contribution in https://github.com/inventree/InvenTree/pull/12423</li>
|
||
<li>@impuls42 made their first contribution in https://github.com/inventree/InvenTree/pull/12432</li>
|
||
<li>@snipe made their first contribution in https://github.com/inventree/InvenTree/pull/12452</li>
|
||
<li>@bhumin18 made their first contribution in https://github.com/inventree/InvenTree/pull/12440</li>
|
||
<li>@hanielee made their first contribution in https://github.com/inventree/InvenTree/pull/12392</li>
|
||
<li>@jayasree-007 made their first contribution in https://github.com/inventree/InvenTree/pull/12533</li>
|
||
</ul>
|
||
|
||
<h3 id="code-contributions">Code Contributions</h3>
|
||
|
||
<p>Check out our GitHub page for a list of <a href="https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22">outstanding issues</a> 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.</p>
|
||
|
||
<h3 id="translation">Translation</h3>
|
||
|
||
<p>Our <a href="https://crowdin.com/project/inventree">translation efforts</a> 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.</p>
|
||
|
||
<p>If you are interested in contributing to the translation efforts, please visit our <a href="https://crowdin.com/project/inventree">Crowdin project</a> and join the community of translators.</p>
|
||
|
||
<h3 id="documentation--technical-writing">Documentation / Technical Writing</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="report-bugs">Report Bugs</h3>
|
||
|
||
<p>If you encounter a bug in InvenTree, please report it on our <a href="https://github.com/inventree/inventree/issues">GitHub issues page</a>. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.</p>
|
||
|
||
<h3 id="financial-contributions">Financial Contributions</h3>
|
||
|
||
<p>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!</p>
|
||
|
||
<p>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!</p>
|
||
|
||
<ul>
|
||
<li><a href="/fund#github-sponsors">GitHub</a></li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>If your company benefits from InvenTree, please consider a <a href="/fund#polar">one time sponsorship</a> or a <a href="/fund#polar">recurring sponsorship</a> to help support the project.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[InvenTree 1.5.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.]]></summary></entry><entry><title type="html">1.4.0 Release</title><link href="/blog/2026/06/16/1.4.0" rel="alternate" type="text/html" title="1.4.0 Release" /><published>2026-06-16T00:00:00+00:00</published><updated>2026-06-16T00:00:00+00:00</updated><id>/blog/2026/06/16/1.4.0</id><content type="html" xml:base="/blog/2026/06/16/1.4.0"><![CDATA[<p>InvenTree 1.4.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>Major changes are documented in the <code class="language-plaintext highlighter-rouge">CHANGELOG.md</code> file in the repository. For a full list of changes, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.4.0">release notes</a>.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h2 id="breaking-changes">Breaking Changes</h2>
|
||
|
||
<p>While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:</p>
|
||
|
||
<h3 id="adjust-api-endpoint-status-code-return-values">Adjust API Endpoint Status Code Return Values</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11723">PR #11723</a> removes various API quirks and aligns the InvenTree API with REST conventions: some operations have been moved to the correct HTTP methods (e.g. GET → POST), HTTP status codes now follow standard conventions rather than custom values, and custom permissions on the notifications endpoint have been removed. Users with custom API integrations should review their code for reliance on the previous non-standard behavior.</p>
|
||
|
||
<h3 id="enforce-order-issued_by-field-as-read-only">Enforce Order “issued_by” Field as Read-Only</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11816">PR #11816</a> makes the <code class="language-plaintext highlighter-rouge">issued_by</code> field on BuildOrder (and related order models) read-only in the API; it is now automatically populated with the user who created the order and can no longer be manually overridden. Any integrations or scripts that previously wrote to this field will need to be updated.</p>
|
||
|
||
<h3 id="nodejs-build-environment-upgraded-to-v24">Node.js Build Environment Upgraded to v24</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11893">PR #11893</a> upgrades the frontend build environment from Node.js 20 (which reached end-of-life on April 30, 2025) to Node.js 24. Developers building InvenTree from source must upgrade their local Node.js installation to v24 or later.</p>
|
||
|
||
<h3 id="report-and-label-plugin-context-changes">Report and Label Plugin Context Changes</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11941">PR #11941</a> fixes a long-standing bug where user information was unavailable in report and label generation contexts. As part of this fix, the signatures for custom report plugin methods (<code class="language-plaintext highlighter-rouge">add_report_context()</code>, <code class="language-plaintext highlighter-rouge">add_label_context()</code>, and <code class="language-plaintext highlighter-rouge">report_callback()</code>) have changed: they now receive an explicit <code class="language-plaintext highlighter-rouge">user</code> object instead of a <code class="language-plaintext highlighter-rouge">request</code> object (which was previously always <code class="language-plaintext highlighter-rouge">None</code> in background workers). Plugin developers must update their implementations accordingly.</p>
|
||
|
||
<h3 id="remove-remote-image-download-support">Remove Remote Image Download Support</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11962">PR #11962</a> removes the <code class="language-plaintext highlighter-rouge">remote_image</code> field from the Part API endpoint, eliminating the ability to supply a remote URL to download a part image from an external source. This feature was removed due to security concerns around server-side outgoing requests; image uploads via other mechanisms (such as clipboard paste) remain supported.</p>
|
||
|
||
<h3 id="fix-resistor-rkm-notation-parsing">Fix Resistor RKM Notation Parsing</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12065">PR #12065</a> corrects how RKM-style resistor values (e.g. <code class="language-plaintext highlighter-rouge">10R</code>, <code class="language-plaintext highlighter-rouge">4R7</code>) are parsed by ensuring the <code class="language-plaintext highlighter-rouge">R</code> delimiter is interpreted as ohms rather than being misread by the unit parser. Parts or parameters that previously relied on the incorrect parsing behavior may need to be reviewed.</p>
|
||
|
||
<h3 id="fix-meaning-of-shipped-status-in-salesorderstatusgroups">Fix Meaning of SHIPPED Status in SalesOrderStatusGroups</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12107">PR #12107</a> corrects a misclassification of the <code class="language-plaintext highlighter-rouge">SHIPPED</code> sales order status: it has been moved from the <code class="language-plaintext highlighter-rouge">COMPLETE</code> group to the <code class="language-plaintext highlighter-rouge">ACTIVE</code> group in <code class="language-plaintext highlighter-rouge">SalesOrderStatusGroups</code>. Any external code or integrations that filter orders based on these status groups will need to be updated to reflect this corrected grouping.</p>
|
||
|
||
<h3 id="report-printing-permission-enforcement">Report Printing Permission Enforcement</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12142">PR #12142</a> tightens permissions for report and label printing: users must now have <code class="language-plaintext highlighter-rouge">VIEW</code> permission on the target model in order to print a report against it, and printing against disabled templates is blocked. Users or integrations that previously relied on printing without explicit view permissions may find certain print actions now return a permission error.</p>
|
||
|
||
<h2 id="security-fixes">Security Fixes</h2>
|
||
|
||
<p>A number of security vulnerabilities have been fixed in this release.</p>
|
||
|
||
<h3 id="django-security-update">Django Security Update</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11907">PR #11907</a> bumps Django to the latest security release, addressing vulnerability <a href="https://github.com/advisories/GHSA-5h8x-9c6f-2j8m">GHSA-5h8x-9c6f-2j8m</a>. All users are encouraged to update promptly to benefit from this patch.</p>
|
||
|
||
<h3 id="admin-interface-permission-restrictions">Admin Interface Permission Restrictions</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12036">PR #12036</a> tightens Django admin permissions to align with the API’s own access controls. Scheduled tasks are now read-only in the admin panel and certain actions are restricted to superusers only, reducing the risk of unauthorized modification of critical system configuration through the admin interface.</p>
|
||
|
||
<h3 id="report-printing-permission-enforcement-1">Report Printing Permission Enforcement</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12142">PR #12142</a> enforces that users must hold <code class="language-plaintext highlighter-rouge">VIEW</code> permission on the target model in order to print a report or label against it, and prevents printing against disabled templates. This closes a path by which users could access model data indirectly through the report printing API without the appropriate permissions.</p>
|
||
|
||
<h3 id="switch-nodejs-version-manager-from-n-to-nvm">Switch Node.js Version Manager from n to nvm</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12140">PR #12140</a> replaces the <code class="language-plaintext highlighter-rouge">n</code> Node.js version manager with <code class="language-plaintext highlighter-rouge">nvm</code> (Node Version Manager) in the Docker build and CI environment. Using the officially maintained <code class="language-plaintext highlighter-rouge">nvm</code> toolchain reduces supply-chain risk compared to the third-party <code class="language-plaintext highlighter-rouge">n</code> package.</p>
|
||
|
||
<h3 id="pdf-report-generation-security-hardening">PDF Report Generation Security Hardening</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12160">PR #12160</a> hardens the WeasyPrint-based PDF report generator against two classes of attack. The <code class="language-plaintext highlighter-rouge">file://</code> URI scheme is now fully disabled in report templates, preventing arbitrary server-side file reads, and SSRF protections have been added for remote URL lookups — with remote URL fetching disabled by default. Users whose report templates reference remote URLs will need to explicitly enable that capability via the new configuration setting.</p>
|
||
|
||
<h3 id="api-permissions-fix">API Permissions Fix</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12168">PR #12168</a> improves API security by reducing the scope of permissions required for certain API endpoints.</p>
|
||
|
||
<h3 id="security-advisories">Security Advisories</h3>
|
||
|
||
<p>The following security advisories have been published in relation to this release:</p>
|
||
|
||
<ul>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-45f6-v6jq-99f7</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-7w96-99fj-8g7x</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-568x-qh23-wh8g</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-xjpv-cwpw-7qx8</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-c9wp-mw98-gfrj</li>
|
||
<li>https://github.com/inventree/InvenTree/security/advisories/GHSA-6pm3-m334-mr4j</li>
|
||
</ul>
|
||
|
||
<p>For more information, please refer to our <a href="https://github.com/inventree/InvenTree/security/advisories?state=published">security advisories page</a></p>
|
||
|
||
<h2 id="new-features">New Features</h2>
|
||
|
||
<h3 id="transfer-orders">Transfer Orders</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11281">PR #11281</a> introduces a new Transfer Order type for formalizing and tracking internal stock movements between locations. Users can create transfer orders with specific source and destination locations, allocate stock to line items, and complete the transfer to move inventory — providing a full audit trail for inter-location stock movements.</p>
|
||
|
||
<h3 id="bom-permission-ruleset">BOM Permission Ruleset</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11825">PR #11825</a> adds a dedicated permission ruleset for Bill of Materials management, allowing administrators to control which user groups can view, edit, or modify BOMs independently of other part permissions. Existing user permissions are preserved via a data migration.</p>
|
||
|
||
<h3 id="bom-row-expand">BOM Row Expand</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11809">PR #11809</a> enables multi-level BOM expansion in the UI, letting users expand individual BOM rows to inspect nested subassemblies inline without switching away from the BOM view. A user-level setting controls whether subassembly expansion is shown by default.</p>
|
||
|
||
<h3 id="bom-compare">BOM Compare</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11853">PR #11853</a> adds a BOM comparison tool accessible from the part detail view, allowing side-by-side comparison of two assemblies’ Bills of Materials. Comparisons can also be linked to directly via URL parameters.</p>
|
||
|
||
<h3 id="maximum-stock-level">Maximum Stock Level</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11914">PR #11914</a> adds a maximum stock level field to parts, complementing the existing minimum stock tracking to provide full min/max inventory management. A new “high stock” filter in the part table makes it easy to identify items that have exceeded their upper limit.</p>
|
||
|
||
<h3 id="attachment-image-thumbnails">Attachment Image Thumbnails</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11961">PR #11961</a> improves attachment handling by detecting image attachments and displaying thumbnail previews in the attachment table. This release also adds a configurable maximum file upload size for administrators.</p>
|
||
|
||
<h3 id="sales-order-auto-allocate">Sales Order Auto-Allocate</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12000">PR #12000</a> brings automatic stock allocation to sales orders, matching the existing behavior on build orders. Users can auto-allocate available stock to order line items with configurable sorting preferences (e.g. by expiry date or serial number), and can bulk-delete allocations through the UI and API.</p>
|
||
|
||
<h3 id="stock-item-creation-date">Stock Item Creation Date</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12011">PR #12011</a> adds a <code class="language-plaintext highlighter-rouge">creation_date</code> field to the StockItem model, capturing when each stock item first entered the system. The field is exposed in the API (with filtering and ordering support) and displayed in the stock item table.</p>
|
||
|
||
<h3 id="hot-module-replacement-for-plugins">Hot Module Replacement for Plugins</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12060">PR #12060</a> enables Hot Module Replacement (HMR) and React Fast Refresh in the Vite development server for InvenTree plugins. Plugin developers can now see code changes reflected instantly without a full page reload, significantly speeding up the plugin development workflow.</p>
|
||
|
||
<h3 id="tags-support">Tags Support</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12077">PR #12077</a> introduces a comprehensive tagging system across InvenTree, covering parts, orders, companies, stock items, and more. Tags can be managed via the API and used to filter tables, providing a flexible way to categorize and locate items without changing the data model.</p>
|
||
|
||
<h3 id="saved-table-filter-sets">Saved Table Filter Sets</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12079">PR #12079</a> allows users to save named sets of table filters and reload them with a single click. This is particularly useful for frequently repeated filter configurations across tables and calendar views.</p>
|
||
|
||
<h3 id="calendar-month-scrolling">Calendar Month Scrolling</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12092">PR #12092</a> enables multi-month scrolling in calendar views, making it much easier to plan and schedule across extended time horizons. A configurable “calendar horizon” parameter allows the view to be set back to a single month if preferred.</p>
|
||
|
||
<h3 id="table-column-filters">Table Column Filters</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12103">PR #12103</a> exposes filter controls directly in table column headers, so users can add, edit, or remove filters without opening a separate filter panel. Active filters are also indicated visually on the relevant column headers.</p>
|
||
|
||
<h3 id="remember-last-used-print-template-and-printer">Remember Last Used Print Template and Printer</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12146">PR #12146</a> persists the user’s last selected label template and printer plugin per model type, so the printing dialog reopens with the same settings as the previous session. This eliminates the need to reselect template and printer on every print action.</p>
|
||
|
||
<h3 id="hotkey-helper-modal">Hotkey Helper Modal</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/12128">PR #12128</a> adds a hotkey registration system and a discoverable helper modal that lists all currently active keyboard shortcuts — including those registered by plugins and mounted components. The modal is accessible via the spotlight interface, making it easy for users to find and learn available shortcuts.</p>
|
||
|
||
<h3 id="calendar-event-tooltips">Calendar Event Tooltips</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11980">PR #11980</a> adds detailed tooltips to calendar event entries across purchase order and build calendar views. Hovering over an event now shows contextual information without requiring the user to navigate away from the calendar.</p>
|
||
|
||
<h3 id="line-number-natural-sort">Line Number Natural Sort</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11885">PR #11885</a> fixes the sorting of line numbers on orders so they sort numerically (1, 2, 3, 10) rather than alphabetically (1, 10, 2, 3). This improves the readability of order line items and ensures a more intuitive ordering.</p>
|
||
|
||
<h2 id="bug-fixes">Bug Fixes</h2>
|
||
|
||
<p>As always, we have provided a number of <a href="https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.4.0">bug fixes</a> with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!</p>
|
||
|
||
<h2 id="contributing">Contributing</h2>
|
||
|
||
<p>InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.</p>
|
||
|
||
<h3 id="new-contributors">New Contributors</h3>
|
||
|
||
<p>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:</p>
|
||
|
||
<ul>
|
||
<li>@hartigdan made their first contribution in https://github.com/inventree/InvenTree/pull/11735</li>
|
||
<li>@ZhangzrJerry made their first contribution in https://github.com/inventree/InvenTree/pull/11746</li>
|
||
<li>@DanielDango made their first contribution in https://github.com/inventree/InvenTree/pull/11868</li>
|
||
<li>@robertsilen made their first contribution in https://github.com/inventree/InvenTree/pull/11950</li>
|
||
<li>@Idea-Junkie made their first contribution in https://github.com/inventree/InvenTree/pull/11369</li>
|
||
<li>@xhivo97 made their first contribution in https://github.com/inventree/InvenTree/pull/12060</li>
|
||
<li>@getpwnam made their first contribution in https://github.com/inventree/InvenTree/pull/12078</li>
|
||
<li>@NerosKi made their first contribution in https://github.com/inventree/InvenTree/pull/12094</li>
|
||
<li>@Nasawa made their first contribution in https://github.com/inventree/InvenTree/pull/12151</li>
|
||
<li>@Sanidhyavijay24 made their first contribution in https://github.com/inventree/InvenTree/pull/12146</li>
|
||
<li>@kaizeenn made their first contribution in https://github.com/inventree/InvenTree/pull/12162</li>
|
||
<li>@johnluetke made their first contribution in https://github.com/inventree/InvenTree/pull/11982</li>
|
||
<li>@geekcj12 made their first contribution in https://github.com/inventree/InvenTree/pull/12203</li>
|
||
<li>@aslushnikov made their first contribution in https://github.com/inventree/InvenTree/pull/12219</li>
|
||
<li>@reid-p made their first contribution in https://github.com/inventree/InvenTree/pull/12227</li>
|
||
</ul>
|
||
|
||
<h3 id="code-contributions">Code Contributions</h3>
|
||
|
||
<p>Check out our GitHub page for a list of <a href="https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22">outstanding issues</a> 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.</p>
|
||
|
||
<h3 id="translation">Translation</h3>
|
||
|
||
<p>Our <a href="https://crowdin.com/project/inventree">translation efforts</a> 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.</p>
|
||
|
||
<p>If you are interested in contributing to the translation efforts, please visit our <a href="https://crowdin.com/project/inventree">Crowdin project</a> and join the community of translators.</p>
|
||
|
||
<h3 id="documentation--technical-writing">Documentation / Technical Writing</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="report-bugs">Report Bugs</h3>
|
||
|
||
<p>If you encounter a bug in InvenTree, please report it on our <a href="https://github.com/inventree/inventree/issues">GitHub issues page</a>. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.</p>
|
||
|
||
<h3 id="financial-contributions">Financial Contributions</h3>
|
||
|
||
<p>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!</p>
|
||
|
||
<p>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!</p>
|
||
|
||
<ul>
|
||
<li><a href="/fund#github-sponsors">GitHub</a></li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>If your company benefits from InvenTree, please consider a <a href="/fund#polar">one time sponsorship</a> or a <a href="/fund#polar">recurring sponsorship</a> to help support the project.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[InvenTree 1.4.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.]]></summary></entry><entry><title type="html">1.3.0 Release</title><link href="/blog/2026/04/11/1.3.0" rel="alternate" type="text/html" title="1.3.0 Release" /><published>2026-04-11T00:00:00+00:00</published><updated>2026-04-11T00:00:00+00:00</updated><id>/blog/2026/04/11/1.3.0</id><content type="html" xml:base="/blog/2026/04/11/1.3.0"><![CDATA[<p>The InvenTree team is excited to announce the release of version 1.3.0. This release includes numerous new features, improvements, and bug fixes.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>Major changes are documented in the <code class="language-plaintext highlighter-rouge">CHANGELOG.md</code> file in the InvenTree repository.</p>
|
||
|
||
<p>For a full list of changes made in this release, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.3.0">release notes</a>.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h2 id="breaking-changes">Breaking Changes</h2>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="supplier-part-model-changes">Supplier Part Model Changes</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11303">#11303</a> 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.</p>
|
||
|
||
<p>Previously, the <em>Part</em> model had a <em>default_supplier</em> field, which pointed to a single instance of the <em>SupplierPart</em> model. This field has been removed, and instead the <em>SupplierPart</em> model has a <em>primary</em> 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.</p>
|
||
|
||
<h3 id="plugin-data-import">Plugin Data Import</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11648">#11648</a> 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.</p>
|
||
|
||
<h3 id="sqlite-support">Sqlite Support</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11500">#11500</a> 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.</p>
|
||
|
||
<h2 id="security-fixes">Security Fixes</h2>
|
||
|
||
<p>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 <a href="https://github.com/inventree/InvenTree/blob/master/SECURITY.md">security policy</a>.</p>
|
||
|
||
<h3 id="advisories">Advisories</h3>
|
||
|
||
<p>The following security advisories have been resolved in this release:</p>
|
||
|
||
<ul>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m">GHSA-cx85-vr3q-9x4m</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-m8j2-vfmq-p6qg">GHSA-m8j2-vfmq-p6qg</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-rhc5-7c3r-c769">GHSA-rhc5-7c3r-c769</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-qh5j-c28q-c4rg">GHSA-qh5j-c28q-c4rg</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-7c3q-vwcv-2vp7">GHSA-7c3q-vwcv-2vp7</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-r8q5-3595-3jh2">GHSA-r8q5-3595-3jh2</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-84jh-x777-8pqq">GHSA-84jh-x777-8pqq</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-m9j7-jw3m-fr22">GHSA-m9j7-jw3m-fr22</a></li>
|
||
</ul>
|
||
|
||
<p>Refer to the individual advisories for more information about the vulnerabilities that were resolved.</p>
|
||
|
||
<h3 id="pull-requests">Pull Requests</h3>
|
||
|
||
<p>In addition to the above advisories, the following pull requests were merged to resolve minor security issues:</p>
|
||
|
||
<ul>
|
||
<li><a href="https://github.com/inventree/InvenTree/pull/11580">#11580</a> - reduces user scope of the <code class="language-plaintext highlighter-rouge">DataOutput</code> API endpoint</li>
|
||
<li><a href="https://github.com/inventree/InvenTree/pull/11602">#11602</a> - reduces user scope of the <code class="language-plaintext highlighter-rouge">DataImport</code> API endpoint</li>
|
||
<li><a href="https://github.com/inventree/InvenTree/pull/11579">#11579</a> - improves data security around static and media file access</li>
|
||
<li><a href="https://github.com/inventree/InvenTree/pull/11659">#11659</a> - adds security banner for superuser accounts</li>
|
||
</ul>
|
||
|
||
<h3 id="project-dependencies">Project Dependencies</h3>
|
||
|
||
<p>We strive to maintain up-to-date dependencies in the InvenTree project, and we have updated a number of dependencies in this release.</p>
|
||
|
||
<h2 id="new-features">New Features</h2>
|
||
|
||
<h3 id="order-line-numbering">Order Line Numbering</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11692">#11692</a> 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.</p>
|
||
|
||
<h3 id="generic-parameter-filtering">Generic Parameter Filtering</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11383">#11383</a> we have significantly overhauled the “parameter filtering” system, allowing for more flexible grouping / filtering of parameters.</p>
|
||
|
||
<h3 id="import-by-natural-keys">Import by Natural Keys</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11288">#11288</a> 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.</p>
|
||
|
||
<h3 id="auto-allocate-tracked-parts">Auto-Allocate Tracked Parts</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/10887">#10887</a> 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.</p>
|
||
|
||
<h3 id="copy-data-cells">Copy Data Cells</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11406">#11406</a> 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.</p>
|
||
|
||
<h3 id="zero-quantity-bom">Zero Quantity BOM</h3>
|
||
|
||
<p>In <a href="https://github.com/inventree/InvenTree/pull/11437">#11437</a> 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.</p>
|
||
|
||
<h3 id="plugin-cache-busting">Plugin Cache Busting</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11565">#11565</a> 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 <a href="https://github.com/inventree/plugin-creator">InvenTree plugin creator</a>, this allows plugin developers to easily ensure that users receive the latest version of their plugin assets without needing to worry about caching issues.</p>
|
||
|
||
<h3 id="keep-forms-open">Keep Forms Open</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11074">#11074</a> 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.</p>
|
||
|
||
<h3 id="task-monitoring">Task Monitoring</h3>
|
||
|
||
<p><a href="https://github.com/inventree/InvenTree/pull/11527">#11527</a> 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.</p>
|
||
|
||
<h2 id="bug-fixes">Bug Fixes</h2>
|
||
|
||
<p>As always, we have provided a number of <a href="https://github.com/inventree/InvenTree/pulls?q=is%3Apr%20label%3Abug%20is%3Aclosed%20milestone%3A1.3.0">bug fixes</a> with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!</p>
|
||
|
||
<h2 id="contributing">Contributing</h2>
|
||
|
||
<h3 id="new-contributors">New Contributors</h3>
|
||
|
||
<p>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:</p>
|
||
|
||
<ul>
|
||
<li>@tinpham5614 made their first contribution in https://github.com/inventree/InvenTree/pull/11406</li>
|
||
<li>@JustusRijke made their first contribution in https://github.com/inventree/InvenTree/pull/11411</li>
|
||
<li>@jmerro-c3d made their first contribution in https://github.com/inventree/InvenTree/pull/11374</li>
|
||
<li>@tigger2000ttfn made their first contribution in https://github.com/inventree/InvenTree/pull/11484</li>
|
||
<li>@justynbell made their first contribution in https://github.com/inventree/InvenTree/pull/11508</li>
|
||
<li>@Knirps1 made their first contribution in https://github.com/inventree/InvenTree/pull/11512</li>
|
||
<li>@nino-tan-smartee made their first contribution in https://github.com/inventree/InvenTree/pull/11536</li>
|
||
<li>@bbzylstra made their first contribution in https://github.com/inventree/InvenTree/pull/10862</li>
|
||
<li>@amm10090 made their first contribution in https://github.com/inventree/InvenTree/pull/11612</li>
|
||
<li>@spamik made their first contribution in https://github.com/inventree/InvenTree/pull/11074</li>
|
||
</ul>
|
||
|
||
<h3 id="code-contributions">Code Contributions</h3>
|
||
|
||
<p>Check out our GitHub page for a list of <a href="https://github.com/inventree/InvenTree/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22">outstanding issues</a> 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.</p>
|
||
|
||
<h3 id="translation">Translation</h3>
|
||
|
||
<p>Our <a href="https://crowdin.com/project/inventree">translation efforts</a> 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.</p>
|
||
|
||
<p>If you are interested in contributing to the translation efforts, please visit our <a href="https://crowdin.com/project/inventree">Crowdin project</a> and join the community of translators.</p>
|
||
|
||
<h3 id="report-bugs">Report Bugs</h3>
|
||
|
||
<p>If you encounter a bug in InvenTree, please report it on our <a href="https://github.com/inventree/inventree/issues">GitHub issues page</a>. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.</p>
|
||
|
||
<h3 id="documentation--technical-writing">Documentation / Technical Writing</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="financial-support">Financial Support</h3>
|
||
|
||
<p>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!</p>
|
||
|
||
<p>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!</p>
|
||
|
||
<ul>
|
||
<li><a href="/fund#github-sponsors">GitHub</a></li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>If your company benefits from InvenTree, please consider a <a href="/fund#polar">one time sponsorship</a> or a <a href="/fund#polar">recurring sponsorship</a> to help support the project.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[The InvenTree team is excited to announce the release of version 1.3.0. This release includes numerous new features, improvements, and bug fixes.]]></summary></entry><entry><title type="html">1.2.7 Release</title><link href="/blog/2026/04/07/1.2.7" rel="alternate" type="text/html" title="1.2.7 Release" /><published>2026-04-07T00:00:00+00:00</published><updated>2026-04-07T00:00:00+00:00</updated><id>/blog/2026/04/07/1.2.7</id><content type="html" xml:base="/blog/2026/04/07/1.2.7"><![CDATA[<p>The InvenTree team has now released version 1.2.7, which includes a number of bug fixes related to security issues which have been identified by the community. We recommend all users to update to this version as soon as possible.</p>
|
||
|
||
<h3 id="changelog">Changelog</h3>
|
||
|
||
<p>For a full list of changes made in this release, please refer to the <a href="https://github.com/inventree/InvenTree/releases/tag/1.2.7">release notes</a>.</p>
|
||
|
||
<h3 id="security-advisories">Security Advisories</h3>
|
||
|
||
<p>The InvenTree development team has been working closely with the community to identify and resolve security issues in the InvenTree codebase. We have published the following <a href="https://github.com/inventree/InvenTree/security/advisories">security advisories</a> related to this release:</p>
|
||
|
||
<ul>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-84jh-x777-8pqq">GHSA-84jh-x777-8pqq</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-r8q5-3595-3jh2">GHSA-r8q5-3595-3jh2</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-7c3q-vwcv-2vp7">GHSA-7c3q-vwcv-2vp7</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-qh5j-c28q-c4rg">GHSA-qh5j-c28q-c4rg</a></li>
|
||
<li><a href="https://github.com/inventree/InvenTree/security/advisories/GHSA-m9j7-jw3m-fr22">GHSA-m9j7-jw3m-fr22</a></li>
|
||
</ul>
|
||
|
||
<p>For specific information regarding the vulnerabilities that have been fixed in this release, please refer to the individual advisories linked above.</p>
|
||
|
||
<h3 id="update-procedure">Update Procedure</h3>
|
||
|
||
<p>To update to the latest version of InvenTree, please follow the updating instructions provided in the <a href="https://docs.inventree.org">InvenTree documentation</a>. Note that the particular update procedure may vary depending on your installation method.</p>
|
||
|
||
<h3 id="acknowledgements">Acknowledgements</h3>
|
||
|
||
<p>We would like to express our thanks to the community members who have contributed to identifying and resolving security issues in the InvenTree codebase. Your contributions are greatly appreciated and help to make InvenTree a more secure and reliable tool for everyone.</p>]]></content><author><name>SchrodingersGat</name></author><summary type="html"><![CDATA[The InvenTree team has now released version 1.2.7, which includes a number of bug fixes related to security issues which have been identified by the community. We recommend all users to update to this version as soon as possible.]]></summary></entry><entry><title type="html">Action required - Upcoming Security Release</title><link href="/blog/2026/03/25/security-release" rel="alternate" type="text/html" title="Action required - Upcoming Security Release" /><published>2026-03-25T00:00:00+00:00</published><updated>2026-03-25T00:00:00+00:00</updated><id>/blog/2026/03/25/security-release</id><content type="html" xml:base="/blog/2026/03/25/security-release"><![CDATA[<p>The InvenTree core development team has received a report of a <em>critical security vulnerability</em> affecting a large range of releases since 2024. We will release a disclosure and a fixed release for the 1.2.x release series on 2026-04-08 21:00 UTC.<br />
|
||
The vulnerability allows for lateral movement and privilege escalation within an InvenTree instance. It has a low attack complexity.</p>
|
||
|
||
<h2 id="steps-to-take-now">Steps to take now</h2>
|
||
|
||
<p>We are not aware of active exploitation of this vulnerability, but we recommend that users take the following steps to mitigate risks:</p>
|
||
<ul>
|
||
<li>Do <em>not</em> expose your InvenTree instance to the public internet without hardening steps as laid out in the <a href="https://docs.inventree.org/en/stable/concepts/threat_model/">threat model</a></li>
|
||
<li>Ensure <em>registration is disabled</em> till the release</li>
|
||
<li>Ensure you <em>trust all users registered</em> on your instance, especially those with staff or higher permissions</li>
|
||
</ul>
|
||
|
||
<p>The vulnerability has a low complexity and can be expected to be exploited once released. It is important to prepare to update or take your system off the public internet.</p>
|
||
|
||
<h2 id="security-policy">Security Policy</h2>
|
||
|
||
<p>As always with security related themes we remind all users, security researchers, and intrested parties of our <a href="https://inventree.readthedocs.io/en/stable/security/">security policy</a>.</p>
|
||
|
||
<p>If you have discovered a security vulnerability, please report it to us via the channels described in the policy. We take all reports seriously and will work to address any vulnerabilities in a timely manner.</p>
|
||
|
||
<p>We would like to thank the security researcher who reported this and several other vulnerabilities in a responsible manner, and we encourage others to do the same in the future. The reporter will be credited in the disclosure and CVE entry.</p>]]></content><author><name>matmair</name></author><summary type="html"><![CDATA[The InvenTree core development team has received a report of a critical security vulnerability affecting a large range of releases since 2024. We will release a disclosure and a fixed release for the 1.2.x release series on 2026-04-08 21:00 UTC. The vulnerability allows for lateral movement and privilege escalation within an InvenTree instance. It has a low attack complexity.]]></summary></entry></feed> |