Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Before you start working on a security issue, ensure that you have a GitHub security advisory that has been created by the security working group or yourself.

  2. On the advisory, create a new private fork on which to make any fixes.

  3. Add your changes to a new branch on the temporary private fork.

  4. Create a new pull request so that your changes can be reviewed.

    1. (warning) The new PR will not run tests because actions workers can’t get access to the private fork. (Link)

      1. image-20240111-193027.pngImage Added
  5. Get the PR reviewed an approved.


    1. Post a Security Announcement 2 business days before merging that you will be merging a security fix and the level of importance of the fix (Example text below, update the date, severity level and second link.)

      Code Block
      A security patch for **openedx/edx-platform** will be added to the **Palm** release and to the current github master branch around [date=2023-07-25 time=15:00:00 timezone="America/New_York"].
      It will fix one security defect with a "critical" [CVSS 3.1 severity rating](
      Details will be published here after release: [GitHub security advisory](
  7. Merge the fix to the current main branch. Backport it to the currently supported named release.