Publishing a new version
2 minute read
The UMH uses the semantic versioning. This article explains how to increase the version number and what steps are needed to take
Create release branch (e.g., 0.6.0) from main. Docker will automatically build Docker containers with the tag
VERSION-prerelease, e.g.,0.6.0-prereleaseCreate PR from release branch to main
Update the helm charts
united-manufacturing-hubby going intoCharts.yamland changing the version to the next version including aprereleaseAdjust repo link
https://repo.umh.appindocs/static/examples/development.yamlto the deploy-preview of helm-repo, e.g.,https://deploy-preview-515--umh-helm-repo.netlify.app/with 515 being the PR created in Step 2. Additionally, add a-develflag the helm install commands, so that helm considers the prerelease as a valid version.Go into the folder
deployment/helm-repoand executehelm package ../united-manufacturing-hub/Go into
deployment/helm-repoand executehelm repo index --url https://deploy-preview-515--umh-helm-repo.netlify.app/ --merge index.yaml .Commit changes. Wait for all container and deploy previews to be created. Conduct test on K300 by specifying the new cloud-init file e.g.,
https://deploy-preview-515--umh-rep.netlify.app/cloud-init/development.yaml(you can create a bit.ly link for that)Test
Conduct steps 3 - 6 with changed version 0.6.0 (instead of 0.6.0-prerelease) and changed repo index url: https://repo.umh.app
Remove old helm packages from prerelease from repo
Merge PR from staging to main
Add a new release containing a changelog of all changes
- Use the github feature to generate the changelogs and create a new section at the top, for release highlights