bump-version

A release workflow for updating AionUi and, when needed, its AionCore dependency. A release is a prepared version of the software made available to users.

In plain words
What is it for?
Use it to prepare patch or specified releases, optionally update AionCore, create a pull request, merge it, and add a version tag.
Why use it?
It gathers release information, checks conditions and files, updates versions, prepares change notes, and handles the Git branch and pull request steps.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/iofficeai/aionui/bump-version
Any agent
npx skills add iOfficeAI/AionUi --skill bump-version
Clone the repo
git clone --depth 1 https://github.com/iOfficeAI/AionUi

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02132
Opus 5 $0.00000 $0.01066
Sonnet 5 $0.00000 $0.00426
Haiku 4.5 $0.00000 $0.00213

Measured yesterday against content hash 3c6131bda7cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bump-version scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/bump-version/SKILL.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bump Version

Automate the AionUi release preparation: query AionCore release → verify artifacts → update versions → generate CHANGELOG → branch → PR → tag.

Usage: /bump-version [version] [flags]

  • /bump-version — auto patch + latest AionCore
  • /bump-version 2.2.0 — explicit AionUi version + latest AionCore
  • /bump-version 2.2.0 --core v0.1.12 — explicit both versions
  • /bump-version --skip-core — pure frontend release (don't touch aioncoreVersion)

Workflow

Step 1: Pre-flight Checks

git branch --show-current
git status --short
  • Not on main → Stop: "Please switch to main before running bump-version."
  • Dirty working tree → Stop: "There are uncommitted changes. Please commit or stash them first."

Step 2: Pull Latest

git pull --rebase origin main

Fails → Stop: "Failed to pull latest code. Please resolve conflicts or network issues first."

Step 3: Determine AionUi Target Version

Read package.json → extract version field.

  • Argument provided → use as-is
  • No argument → parse major.minor.patch, increment patch by 1

Display: "Bumping AionUi: {current} → {target}"

Step 4: Query AionCore Latest Release

Skip entirely if --skip-core is set.

gh release view --repo iOfficeAI/AionCore --json tagName,body
  • If --core <version> provided → use that tag instead of latest
  • Display the AionCore version and ask user to confirm before continuing
  • Also read current aioncoreVersion from package.json — if it already matches the queried version, warn the user and ask whether to proceed or use --skip-core

Step 5: Verify AionCore Artifacts

Skip if --skip-core.

gh release view <tag> --repo iOfficeAI/AionCore --json assets --jq '.assets[].name'

Verify all 7 expected assets exist:

  • aioncore-<tag>-x86_64-unknown-linux-gnu.tar.gz
  • aioncore-<tag>-aarch64-unknown-linux-gnu.tar.gz
  • aioncore-<tag>-x86_64-apple-darwin.tar.gz
  • aioncore-<tag>-aarch64-apple-darwin.tar.gz
  • aioncore-<tag>-x86_64-pc-windows-msvc.zip
  • aioncore-<tag>-aarch64-pc-windows-msvc.zip
  • aioncore-checksums.txt

Read the full file on GitHub · 275 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 275 lines · 0 tokens per session scan A 3c6131bda7cc

Subscribe to this mod's changes

bump-version is a skill published in the GitHub repository iOfficeAI/AionUi (32,427 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,132 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.