github.com/iter8-tools/iter8@v1.1.2/bump-version-hints.md (about) 1 These instructions are a guide to making a new major or minor (not patch) release. The challenge is that charts refer to the image version. But this version is only created when the release is published. Consequently the following sequence of steps is needed: 2 3 1. Modify only golang code (no version bump) 4 1. Do not change `MajorMinor` or `Version` in `base/util.go` 5 6 Make new major/minor release 7 8 2. Bump version references in `/charts` changes and bump `/charts/iter8` chart version (no changes to `/testdata`) and bump Kustomize files and bump verifyUserExperience workflow 9 1. The charts are modified to use the new image 10 2. The chart versions should be bumped to match the major/minor version (this is required for the `iter8` chart) but is desirable for all 11 12 Merging the chart changes triggers a automatic chart releases 13 14 3. Version bump golang and `/testdata` and other workflows 15 1. Bump `MajorMinor` or `Version` in `base/util.go` 16 2. Bump explicit version references in remaining workflows 17 3. Bump Dockerfile 18 5. Changes to `/testdata` is only a version bump in charts (`iter8.tools/version`) 19 20 Make a release (new patch version) 21 22 *** 23 24 At this point the documentation can be updated to refer to the new version. This usually takes 2 commits (or one with failed link checking) 25 26 Some things to change in the docs: 27 28 * `iter8.tools/version` in Kubernetes manifests samples 29 * `--version` for any `helm upgrade` and `helm template` commands 30 * `getting-started/delete.md.md` and `getting-started/install.md` 31 * Reference to `values.yaml`