Skip to content
Back to skills

Client Version Bump

ASecurity

How to bump the web client version in the jean2 monorepo. Load when releasing or versioning client changes.

  • 33 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agents

Works with

  • cli

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add prokopai/prokop --skill client-version-bump --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Client Version Bump?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Client Version Bump
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/prokopai-client-version-bump/badge)](https://www.skillsdirectory.com/skills/prokopai-client-version-bump)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: client-version-bump
description: How to bump the web client version in the jean2 monorepo. Load when releasing or versioning client changes.
---

# Client Version Bump (jean2 monorepo)

Procedural guide for bumping the web client version. Server and SDK are versioned separately and must NOT be touched.

## File to update

| File | Format |
|------|--------|
| `packages/client/package.json` | `"version": "X.Y.Z"` |

## Do NOT touch these during a manual bump

- `packages/client/VERSION` - do not update it during a package version change. `package.json` is the build version source.
- `packages/sdk/package.json` — versioned independently
- `packages/server/package.json` — versioned independently
- `packages/sdk/src/version.ts`, `packages/server/src/version.ts` — separate

## Procedure

1. Determine the new version number (e.g. `1.1.0` -> `1.1.1` for a patch).
2. Update `packages/client/package.json` to the new version.
3. Create changelog: `changelogs/client/vX.Y.Z.md`
4. Run `bun run typecheck` to verify nothing broke.

## Changelog format

Follow the style of existing entries in `changelogs/client/`. Sections:

- `### Added` for new features
- `### Changed` for modifications to existing behavior
- `### Fixed` for bug fixes
- `### Removed` for deleted features

Each entry is a bullet starting with **bold summary** followed by a colon and description. Only include sections that have entries. Do NOT use em-dashes anywhere (user preference).

Example:

```markdown
### Changed

- **Structured output visual overhaul**: structured responses now render array items as bordered cards with numbered index badges, use a compact definition-list layout for nested objects, and render markdown syntax in string values.
```

## Verification

After updating, confirm the client version and verify SDK and server are unchanged:

```sh
grep '"version"' packages/client/package.json packages/sdk/package.json packages/server/package.json
```

Do not modify `packages/client/VERSION` as part of the version change.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.