agentrium: Command for Claude Code

Publish a new release of Agentrium

You are performing a full release of Agentrium. Follow every step below in order. Stop and ask the user if anything is ambiguous or fails.

Arguments

$ARGUMENTS - The new version number (e.g. 1.6.0). If not provided, ask the user what version to publish.

Step 1: Validate

1. Confirm the version number with the user before proceeding.
2. Read the current version from package.json and verify the new version is higher.
3. Ensure the working tree is clean (git status). If there are uncommitted changes, warn the user and ask whether to proceed or abort.
4. Ensure you are on the master branch. If not, warn the user.

Step 2: Bump version in all files

Update the version string in all five of these files (replace the old version with the new one):

1. package.json - the "version" field
2. src-tauri/Cargo.toml - the version field under [package]
3. src-tauri/tauri.conf.json - the "version" field
4. README.md - update these version references (link text AND URL for each row of the Download table):
   • The version badge: version-X.Y.Z-green
   • Windows NSIS: Agentrium_X.Y.Z_x64-setup.exe
   • Windows MSI: Agentrium_X.Y.Z_x64_en-US.msi
   • macOS Apple Silicon: Agentrium_X.Y.Z_aarch64.dmg
   • macOS Intel: Agentrium_X.Y.Z_x64.dmg
   • Every row must be a real [filename](https://github.com/talayash/agentrium/releases/latest/download/filename) link, not a bare backtick code span.
5. CLAUDE.md - the Current version: **X.Y.Z** line

After editing, verify each file was updated correctly by reading the changed lines.

Step 2b: Add changelog entry

Add a new entry at the top of the src/changelog.json array for this version. Ask the user for a summary of the features/changes to include. Each entry has this format:

{
  "version": "X.Y.Z",
  "date": "YYYY-MM-DD",
  "features": [
    { "title": "Fix bugs & performance" },
    { "title": "Feature name", "description": "Optional description" }
  ]
}