# Set Version > Updates GG's version number for all components. Use when asked to update the version or create releases. - Skill: `gulbanana/set-version` (Agent Skill) - Install (CLI): `npx skillmds@latest add gulbanana/set-version` - Raw SKILL.md: https://api.skillmd.com/api/skills/gulbanana/set-version/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: gulbanana (https://skillmd.com/u/gulbanana) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/gulbanana/set-version --- GG has multiple components: a Rust crate, a Node package and a Tauri application. All of these need to be kept in sync, as does the documentation. The versioning numbering scheme is 0.xx.y, where xx is the JJ version number and y is the number of a GG release for that JJ version. For example, the first GG release for JJ 0.37.0 was called GG 0.38.0, and the second was called GG 0.38.1. Version update procedure ======================== 1. Set package.version in `Cargo.toml`. 2. Run `cargo update`. 3. Set "version" in `package.json`. 4. Run `npm update`. 5. Set version in `Tauri.toml`. 6. Update CHANGELOG.md. 7. `jj commit -m "version number"` CHANGELOG.md update procedure ============================= We follow the https://keepachangelog.com/ standard. The first "##" second-level header in CHANGELOG.md will be either a version number or "[Unreleased]". - If it's `[Unreleased]`, it should be replaced with this pattern: `[0.xx.y](releases/tag/v0.xx.y)`. This links to the tag that will later be created on GitHub. - If it already matches the correct pattern, there's no need to update it further. - If it's anything else, that's a problem - it means the release doesn't have changelog entries. Notify the user about this and stop! In any case, if this is a .0 update (the first for a given JJ version), ensure that the first line after the second-level header is `This release is based on Jujutsu 0.xx.`.