<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Source Upgrades on DefectDojo Documentation</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/</link><description>Recent content in Open Source Upgrades on DefectDojo Documentation</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2025 DefectDojo, Inc.</copyright><atom:link href="https://beta-docs.defectdojo.com/releases/os_upgrading/index.xml" rel="self" type="application/rss+xml"/><item><title>Open Source Upgrading</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/upgrading_guide/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/upgrading_guide/</guid><description>&lt;h2 id="docker-compose"&gt;Docker compose&lt;/h2&gt;
&lt;p&gt;When you deploy a vanilla docker compose, it will create a persistent
volume for your Postgres database. As long as your volume is there, you
should not lose any data.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.4.300</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.300/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.300/</guid><description>&lt;h2 id="the-endpoint-field-of-apiv2endpoint_status"&gt;The &lt;code&gt;endpoint&lt;/code&gt; field of &lt;code&gt;/api/v2/endpoint_status/&lt;/code&gt;&lt;/h2&gt;
&lt;p&gt;With Locations enabled, the &lt;code&gt;endpoint&lt;/code&gt; field of &lt;code&gt;/api/v2/endpoint_status/&lt;/code&gt; now carries the &lt;code&gt;id&lt;/code&gt; that
&lt;code&gt;/api/v2/endpoints/&lt;/code&gt; lists for the Finding&amp;rsquo;s Asset, the same ID the &lt;code&gt;?endpoint=&lt;/code&gt; filter takes. It
used to carry the Location&amp;rsquo;s ID, which only matched &lt;code&gt;/api/v2/endpoints/&lt;/code&gt; when the two IDs happened
to be equal. The Location&amp;rsquo;s ID is still in &lt;code&gt;location_id&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.4.200</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.200/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.200/</guid><description>&lt;h2 id="defectdojo-pro-the-classic-sidebar-is-removed"&gt;DefectDojo Pro: the classic sidebar is removed&lt;/h2&gt;
&lt;p&gt;The reorganized sidebar is now the only navigation in the DefectDojo Pro UI. The classic
sidebar and the &lt;strong&gt;Menu 2.0&lt;/strong&gt; toggle on the Feature Flags page are removed. This change applies
to DefectDojo Pro only. The open source UI is unaffected.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.4.100</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.100/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4.100/</guid><description>&lt;h2 id="deprecated-api-endpoints-corrected-end-of-life-date"&gt;Deprecated API endpoints: corrected end-of-life date&lt;/h2&gt;
&lt;p&gt;The deprecated Tool Type, Tool Configuration, and API Scan Configuration API endpoints send a
corrected end-of-life date. They now send &lt;code&gt;X-End-Of-Life-Date: 2026-11-02T00:00:00&lt;/code&gt;, the actual
3.5.0 release day. The earlier value was &lt;code&gt;2026-11-01T00:00:00&lt;/code&gt;, one day off.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.5.x</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.5/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.5/</guid><description>&lt;p&gt;There are no special instructions for upgrading to 3.5.x beyond the API change below. Check the &lt;a href="https://github.com/DefectDojo/django-DefectDojo/releases/tag/3.5.0"&gt;Release Notes&lt;/a&gt; for the contents of the release.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.3.200</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.3.200/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.3.200/</guid><description>&lt;h2 id="feature-flags-toggles-reach-the-classic-ui-and-apiv2-after-a-restart-defectdojo-pro"&gt;Feature Flags toggles reach the Classic UI and &lt;code&gt;/api/v2&lt;/code&gt; after a restart (DefectDojo Pro)&lt;/h2&gt;
&lt;p&gt;Two features on the &lt;strong&gt;Settings &amp;gt; Feature Flags&lt;/strong&gt; page, &lt;strong&gt;Locations&lt;/strong&gt; and &lt;strong&gt;Organization / Asset Relabeling&lt;/strong&gt;, have parts that are decided when DefectDojo starts: the Classic UI pages and labels, the &lt;code&gt;/api/v2&lt;/code&gt; endpoint and location routes, and the &lt;code&gt;/api/v3/&lt;/code&gt; API. Both carry a &lt;strong&gt;Restart Recommended&lt;/strong&gt; tag for that reason.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.4.x</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.4/</guid><description>&lt;p&gt;There are no special instructions for upgrading to 3.4.x. Check the &lt;a href="https://github.com/DefectDojo/django-DefectDojo/releases/tag/3.4.0"&gt;Release Notes&lt;/a&gt; for the contents of the release.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.2.200</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.2.200/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.2.200/</guid><description>&lt;h2 id="locations-is-now-a-self-service-toggle-defectdojo-pro"&gt;Locations is now a self-service toggle (DefectDojo Pro)&lt;/h2&gt;
&lt;p&gt;In DefectDojo Pro, &lt;strong&gt;Locations&lt;/strong&gt; moves from an environment-managed setting to a &lt;strong&gt;database-backed toggle&lt;/strong&gt; on the &lt;strong&gt;Settings &amp;gt; Feature Flags&lt;/strong&gt; page. You no longer need a deployment change or a Support request to turn it on: the toggle drives the Pro UI and the import pipeline live, with no restart.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.2.100</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.2.100/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.2.100/</guid><description>&lt;h2 id="private-notes-are-now-limited-to-their-author"&gt;Private notes are now limited to their author&lt;/h2&gt;
&lt;p&gt;Before 3.2.100, a note marked &lt;strong&gt;Private&lt;/strong&gt; was still served to every user who could view the object it was attached to. The flag changed how the note was labelled, not who received it.&lt;/p&gt;</description></item><item><title>Upgrading to DefectDojo Version 3.3.x</title><link>https://beta-docs.defectdojo.com/releases/os_upgrading/3.3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beta-docs.defectdojo.com/releases/os_upgrading/3.3/</guid><description>&lt;h2 id="deduplication-identity-changes"&gt;Deduplication identity changes&lt;/h2&gt;
&lt;p&gt;Three scan types gain &lt;code&gt;HASHCODE_FIELDS_PER_SCANNER&lt;/code&gt; registrations in this release. A
registration changes how &lt;code&gt;hash_code&lt;/code&gt; is computed, so findings imported by these parsers
before the upgrade carry a hash that no longer matches what an import computes after it.
Left alone, the next re-import of an unchanged report would treat every affected finding
as new, close the stored one as absent, and recreate it, detaching false positive
history and risk acceptances along the way.&lt;/p&gt;</description></item></channel></rss>