version-update

Synchronize project versions across ols/version.py, docs/openapi.json, and scripts/build-container.sh.

71|88|Updated Nov 8, 2023
One-click install
npx skills add https://github.com/openshift/lightspeed-service --skill version-update-openshift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-update
Source: https://github.com/openshift/lightspeed-service/tree/main/.cursor/skills/version-update
Command: npx skills add https://github.com/openshift/lightspeed-service --skill version-update-openshift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the codebase in sync by updating the OLS version across multiple files to avoid drift during releases.

Core Features & Use Cases

  • Updates the version in ols/version.py, docs/openapi.json, and scripts/build-container.sh so all references match.
  • Supports standard release workflows and hotfix scenarios requiring a single source of truth.
  • Suitable for CI pipelines that enforce version consistency before packaging.

Quick Start

Run the version-update operation after bumping the version to ensure all target files reflect the new version.

Frequently Asked Questions about version-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize project version numbers across multiple files for a release?

To synchronize project version numbers, this automation validates and updates version references in ols/version.py, docs/openapi.json, and scripts/build-container.sh, ensuring all three match and enforcing a single source of truth for releases.

What is the best way to prevent version drift in CI pipelines before packaging?

Preventing version drift in CI pipelines requires enforcing version consistency across core files. This automation validates that references in version.py, openapi.json, and build-container.sh match, updating them if needed before packaging.

How does version synchronization work for OpenShift release management?

Version synchronization works by automating the update of the OLS version across multiple codebase files. It checks ols/version.py, docs/openapi.json, and scripts/build-container.sh, updating any mismatches to maintain a single source of truth.

Can I use this to update version references for hotfix scenarios?

Yes, you can use this for hotfix scenarios. It supports standard release workflows and hotfix patches by updating the version across version.py, openapi.json, and build-container.sh to ensure all references match consistently.

When do I need to run version updates during release preparation?

You need to run version updates after bumping the version during release preparation. This ensures all target files, including version.py, openapi.json, and build-container.sh, reflect the new version and remain synchronized.