DefectDojo Release Update: 3.0 Timeline and 2.59.x Removal Plan

Greg A. · 2026-06-08T18:49:27.400Z

Release Update: 3.0 Timeline and 2.59.x DefectDojo Community, A quick update on the 3.0 release. We originally planned to ship DefectDojo 3.0 on June 1, but during the release process we ran into a few issues and the build went out as 2.59.x instead. The 2.59.x release has a few issues including the version 2/3 UI toggling and the fact that it isn’t labeled 3.0, which complicates versioning and image management. This Monday, instead of our usual minor release, we will focus on removing 2.59. A release this big is worth getting right, so we're taking the time to do it properly. We are not planning to do any minor releases until 3.x is out. We expect to resume our normal cadence with the correct 3.x release in early July. Thank you for your patience.

DefectDojo Release Update: 3.0 Timeline and 2.59.x Removal Plan | DefectDojo Community

12 comments

· Sorted by Oldest

callard
·
(edited)·
Just to make you aware if you did roll up to version 2.59, doing a subsequent docker compose pull causes the now 2.58.4 version you have inadvertently pulled to not be able to start correctly due to a missing table that I believe was for the the deprecated credential manager feature
callard
·
·
re creating the table allows you to get back in which is how I fixed mine, I did not have any data in there as I wasn't using the feature.
callard
·
·
callard
·
·
^ for reference
callard
·
·
callard
·
·
callard
·
·
callard
·
·
I can make a github bug report if needed, just want to get this in front of you guys
callard
·
·
"Warning: Unable to load system settings from database: column dojo_system_settings.enable_credentials does not exist LINE 1: ...ings"."risk_acceptance_notify_before_expiration", "dojo_syst... ^. Default values are being used. Please check your database configuration and run migrations if needed." additional error once in, showing in the banner ^
callard
·
·
seems to be a similar issue of things removed moving to 2.59 that aren't handled well when downgrading
Greg A.
·
·
Thanks for digging into this and writing it up so clearly. This kind of report really helps us. 3.0 was meant to be fully downgrade-compatible, but the planned deprecation of the credentials manager pulled out the table and column behind it, which broke compatibility on the way back down. We'll get it corrected with 3.0. I'm not sure what else we can do right now to help others. Your workaround of recreating the table is very helpful for anyone stuck right now. We're hoping that pulling 2.59 in the meantime will help reduce the impact while we work on a fix. Yes please, a GitHub bug report would be a big help. It lets us track it properly. Thank you again.
Valentijn S.
·
·
https://github.com/DefectDojo/django-DefectDojo/issues/14988

callard
·
(edited)·
Just to make you aware if you did roll up to version 2.59, doing a subsequent docker compose pull causes the now 2.58.4 version you have inadvertently pulled to not be able to start correctly due to a missing table that I believe was for the the deprecated credential manager feature
callard
·
·
re creating the table allows you to get back in which is how I fixed mine, I did not have any data in there as I wasn't using the feature.
callard
·
·
callard
·
·
^ for reference
callard
·
·
callard
·
·
callard
·
·
callard
·
·
I can make a github bug report if needed, just want to get this in front of you guys
callard
·
·
"Warning: Unable to load system settings from database: column dojo_system_settings.enable_credentials does not exist LINE 1: ...ings"."risk_acceptance_notify_before_expiration", "dojo_syst... ^. Default values are being used. Please check your database configuration and run migrations if needed." additional error once in, showing in the banner ^
callard
·
·
seems to be a similar issue of things removed moving to 2.59 that aren't handled well when downgrading
Greg A.
·
·
Thanks for digging into this and writing it up so clearly. This kind of report really helps us. 3.0 was meant to be fully downgrade-compatible, but the planned deprecation of the credentials manager pulled out the table and column behind it, which broke compatibility on the way back down. We'll get it corrected with 3.0. I'm not sure what else we can do right now to help others. Your workaround of recreating the table is very helpful for anyone stuck right now. We're hoping that pulling 2.59 in the meantime will help reduce the impact while we work on a fix. Yes please, a GitHub bug report would be a big help. It lets us track it properly. Thank you again.
Valentijn S.
·
·
https://github.com/DefectDojo/django-DefectDojo/issues/14988