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:
- Modify only golang code (no version bump)
- Do not change
MajorMinor
orVersion
inbase/util.go
- Do not change
Make new major/minor release
- Bump version references in
/charts
changes and bump/charts/iter8
chart version (no changes to/testdata
) and bump Kustomize files and bump verifyUserExperience workflow- The charts are modified to use the new image
- The chart versions should be bumped to match the major/minor version (this is required for the
iter8
chart) but is desirable for all
Merging the chart changes triggers a automatic chart releases
- Version bump golang and
/testdata
and other workflows- Bump
MajorMinor
orVersion
inbase/util.go
- Bump explicit version references in remaining workflows
- Bump Dockerfile
- Changes to
/testdata
is only a version bump in charts (iter8.tools/version
)
- Bump
Make a release (new patch version)
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)
Some things to change in the docs:
iter8.tools/version
in Kubernetes manifests samples--version
for anyhelm upgrade
andhelm template
commandsgetting-started/delete.md.md
andgetting-started/install.md
- Reference to
values.yaml