OpenParable
Skip to content
← Back to skills

Set Version

Development
set-version

Set Version is an Agent Skill for development published in the gulbanana/gg repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Updates GG's version number for all components. Use when asked to update the version or create releases.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/gulbanana/gg/blob/HEAD/.claude/skills/set-version/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/set-version, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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..