Run any Skill in Manus with one click

update-version

Stars8

Forks35

UpdatedMarch 19, 2026 at 05:02

Update the project version number across all files that contain it on the current branch. Use when bumping the version on a single branch only. For a full multi-branch release, use the release skill instead.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

openshift

openshift/lightspeed-console

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	update-version
description	Update the project version number across all files that contain it on the current branch. Use when bumping the version on a single branch only. For a full multi-branch release, use the release skill instead.

Update Version

Steps

Determine the new version. If the user didn't specify one, read the current version from package.json and bump the patch version number.
Update package.json — replace the version string in both the top-level version field and the consolePlugin.version field. Both must match.
Update src/components/OverviewDetail.tsx — replace the old version string in the JSX with the new one.
Sync the lockfile — run npm install to propagate the version change into package-lock.json.
Verify — search the workspace for the old version string to confirm no stale references remain (ignore node_modules/ and dist/). Report any unexpected occurrences to the user.

Version format

This project uses semver (MAJOR.MINOR.PATCH)

More from this repository

same repository

test

openshift/lightspeed-console

Run end-to-end tests filtered by tag. Use when the user asks to run tests, run Playwright, or test a specific feature tag like @core or @attach.

2026-06-018

unused-exports

openshift/lightspeed-console

Find exported symbols that are never imported by another file. Use when the user says "check exports", "unused exports" or asks to clean up exports.

2026-05-158

code-review

openshift/lightspeed-console

Review a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name.

2026-04-208

rebase

openshift/lightspeed-console

Rebase the current branch onto its base branch, resolve all conflicts, and verify lint, i18n, and build pass. Use when the user asks to rebase, update, or sync a branch with its upstream base.

2026-04-208

backport

openshift/lightspeed-console

Backport commits or PRs from main to a release branch. Use when the user asks to backport, cherry-pick, or port changes between branches, or when resolving conflicts from a cherry-pick onto a release branch.

2026-04-108

release

openshift/lightspeed-console

Bump the project version across all release branches and commit the changes. Use when the user asks to do a release or update the version on all branches.

2026-04-108

name	update-version
description	Update the project version number across all files that contain it on the current branch. Use when bumping the version on a single branch only. For a full multi-branch release, use the release skill instead.

Update Version

Steps

Determine the new version. If the user didn't specify one, read the current version from package.json and bump the patch version number.
Update package.json — replace the version string in both the top-level version field and the consolePlugin.version field. Both must match.
Update src/components/OverviewDetail.tsx — replace the old version string in the JSX with the new one.
Sync the lockfile — run npm install to propagate the version change into package-lock.json.
Verify — search the workspace for the old version string to confirm no stale references remain (ignore node_modules/ and dist/). Report any unexpected occurrences to the user.

Version format

This project uses semver (MAJOR.MINOR.PATCH)