Upgrading Software Risk Manager

This section details how to upgrade Software Risk Manager to the latest version.

Note: It is recommended that you create a backup of your Software Risk Manager Docker Compose environment before upgrading to the latest Software Risk Manager version.

Remove your Software Risk Manager container(s) before starting the upgrade. (Do not use the -v switch with the down command because it will delete your data volumes.)

docker-compose -f /path/to/your-docker-compose-file down

The recommended upgrade method is to pull the latest changes from GitHub. The Docker Compose file is updated with each Software Risk Manager release to reference the latest Docker image versions. Edits to local files, such as your Docker Compose file, may block your pull from GitHub, so use the following commands to stash your changes and reapply them after your pull:

cd /path/to/srm-docker
git stash save before-upgrade
git pull
git stash apply

If you see a "Merge conflict" message when you run git stash apply, edit the flagged file to resolve the conflict, then run git add /path/to/file to mark the file as merged.

If you do not want to use Git, you can alternatively download the latest ZIP file from GitHub. (If you use the ZIP to replace an existing folder, you must reapply any local edits, such as the changes you made to your Docker Compose file.)

Once you have the latest changes, run your Docker Compose up command to start Software Risk Manager:

docker-compose -f /path/to/your-docker-compose-file up