Run a release tag, not main. Before moving to a newer one, read what changed
and check your manifests still validate.
You need: a clone installed from source. Private copy? Merge each release instead. Container? Build from the tag.
Fetch the release tags. git describe names the one you're on.
Copy the commands
git describe --tags --match 'v*'
git fetch --tags
git tag -l 'v*'Read every release between yours and the target, and act on each Breaking, Deprecated, and Removed section:
Copy the command
git show v0.5.1-beta:CHANGELOG.md | grep -E '^## \[|^### (Breaking|Deprecated|Removed)'Here, 0.4.0-beta made three KnowBe4 settings required. What each bump means:
| Bump | For you |
|---|---|
| Major | A manifest field, CLI flag, or fetcher output you use can break. |
| Minor | New fetchers and options. Before 1.0, a minor can also break. |
| Patch | Fixes and dependency bumps. |
Switch, reinstall with your extras, and validate each
manifest. Skipping the reinstall can fail with ModuleNotFoundError:
releases add dependencies.
Copy the commands
git switch --detach v0.5.1-beta
pip install -q -e '.[all]'
paramify validate manifests/<your manifest>.yamlSet what it names as the entry says (manifest commands), then validate again.
| Symptom | Fix |
|---|---|
git describe prints v0.5.1-beta-291-g59a2387 |
You're on main, 291 commits past it. Switch to a tag. |
| A run breaks after upgrading | Switch back to your old tag, then reinstall. |
More detail: how releases are cut · CHANGELOG


