Deployment & Release

[frozenhelium]

Here's the process we should follow for the deployment and releases of the GO web app.

1. Make sure all the latest changes are merged into develop branch
2. Make sure you have the latest version of the develop branch locally
3. Update the version using yarn version. Read more about the versioning here.
   • This will create a new commit and a tag
   • Push the commit using git push and the tag using git push origin <tag>
4. Deploy to staging using the Azure pipeline. Make sure to increment the deployment version before starting the pipeline.
   • Deployment version (Version field in pipeline) is different from the app version. For staging, we use the format 1.0.0.XX
   • GitBranch for build should be develop and Environments should be - Stage
5. Create a GH release from the newly added tag
   • Add changelog
   • Mark it as pre-release
6. Make sure the latest version has appeared in the footer and everything is working properly on the staging.

Additionally, for production release.

1. Make sure you have the latest version of develop and release branch locally.
   • NOTE: make sure to use git pull --rebase for the release branch
2. Rebase the release branch with develop
3. Push the release branch
   • Make sure to use --force-with-lease
4. Deploy to production using the Azure pipeline.
   • For production, we use the format 1.0.1.XX for Version
   • GitBranch for the build should be release
5. Make sure the latest version has appeared in the footer after the deployment pipeline is complete

[nanometrenat]

Also need to add the process for updating tickets to reflect the released/not released status so they can be checked and closed.