Branching model

How to create releases

Regular releases

The DefectDojo team aims to release at least once a month, on the first Tuesday. Bugfix or security releases can come at any time.

In doubt, GitHub Actions are the source of truth. The releases are semi-automated right now, with a DefectDojo maintainer proceeding with each major step in the release. The steps for a regular release are:

  1. Create the release branch from dev and prepare a PR against master (details) –> A maintainer verifies and manually merges the PR
  2. Tag, issue draft release and docker build+push (details) –> A maintainer massages the release-drafter notes and publishes the release
  3. A PR to merge master back to dev is created to re-align the branches (details)

Security releases

PRs that relate to security issues are done through security advisories which provide a way to work privately on code without prematurely disclosing vulnerabilities.

Release and hotfix model


Diagrams created with plantUML. Find a web-based editor for PlantUML at


A dev version of the documentation built from the dev branch is available at DefectDojo Documentation - dev branch.

Last modified September 15, 2022: Replace documentation links (#6764) (4d581fc3a)