# Version Update

> Bump the Python package version in pyproject.toml for a release or when the user asks to change the project version.

- Skill: `openshift/version-update` (Agent Skill)
- Install (CLI): `npx skillmds@latest add openshift/version-update`
- Raw SKILL.md: https://api.skillmd.com/api/skills/openshift/version-update/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools, Data & Analytics
- Author: openshift (https://skillmd.com/u/openshift)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/openshift/version-update

---


# Version Update

**Source of truth:** `pyproject.toml` → `[project]` → `version = "X.Y.Z"`.

There is no separate `version.py` or OpenAPI artifact in this repo that must
stay in lockstep; bump the single `version` field unless the user points to
another file that encodes it (e.g. future release automation).

## Checklist

- [ ] `pyproject.toml` `[project].version` updated
- [ ] If release notes or tags are used, mention the same version there (user-directed)

## Notes

- Container image tags are typically driven by CI/Konflux from git revision, not
  this field alone.
- After bumping, run `make verify` and `make test` before tagging or releasing.

