Release a new version
This is a small guide to make a new MedCo release.
- Update the Angular version and ensure node version in docker image is compatible with angular
- NPM packages:
npm updateand review with
keycloak-js: has to be the same version as Keycloak (set in a
typescript: has to be compatible with the angular version used
Dockerfilego base image version:
- go.mod go version:
- Go modules (pay particular attention to onet):
go get -u ./...and
go mod tidy
- Check that all the CI/CD pipeline on GitHub passes (this tests the whole backend with the profile dev-local-3nodes)
- Deploy locally test-local-3nodes to manually test Glowing Bear MedCo
- Deploy locally on several machines test-network to manually test the deployment over several machines, and the generation of its configuration
To change the version of the docker images used, update the
.envfile in the deployment folder:
- Update the version of Glowing Bear MedCo
Makefileto point to the correct Docker tag that will be released (e.g. v1.0.0)
Version numbers follow semantic versioning, and both codebases should have the same version. For both codebases:
- Out of the
devbranch, create a new release (and the associated tag) with the semantic version (e.g. v1.0.0)
- Ensure the CI/CD pipeline correctly builds the new release
- Create new variant named like the MedCo version being release (e.g.
v1.0.0). When merged it will be pushed as a branch on GitHub.
- Update version numbers in the guides' download scripts (e.g.
- Review the documentation to ensure the guides are up-to-date. Notably the deployment and loading guides.
- Make the documentation variant be the new main variant on GitBook.
- On GitHub, set the branch corresponding to the new version be the new default branch.
- Ensure on GitHub that all images have been built correctly with the proper versioning.
- Update medco.epfl.ch website with the new version and update the roadmap.
- Communication about the new release (Twitter notably).