What is bump-version?

A release helper for a Rust and Flatpak desktop app that keeps its version information and release notes aligned across project files. It also checks that the Flatpak package builds.

Use it when publishing a new semantic version such as 0.3.5 of Sessions Chronicle. It updates the listed version files, adds reviewed release notes, and verifies the Flatpak build.

It prevents different files from showing different release versions and catches Flatpak build problems before release. It can also prepare release notes for review when they are missing.

bump-version — Skill for Claude Code and Codex by supermaciz

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.

Any agent

npx skills add supermaciz/sessions-chronicle --skill bump-version

Clone the repo

git clone --depth 1 https://github.com/supermaciz/sessions-chronicle

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/supermaciz/sessions-chronicle/bump-version/github.svg)](https://agentmods.dev/skills/supermaciz/sessions-chronicle/bump-version)

Your own site

<a href="https://agentmods.dev/skills/supermaciz/sessions-chronicle/bump-version"><img src="https://agentmods.dev/badge/skills/supermaciz/sessions-chronicle/bump-version/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/supermaciz/sessions-chronicle/bump-version"><img src="https://agentmods.dev/badge/skills/supermaciz/sessions-chronicle/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,280 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.01280
Opus 5.5	$0.00014	$0.00512
Sonnet 5.5	$0.00007	$0.00256
Haiku 4.5	$0.00003	$0.00128

Measured 2d ago against content hash c9ff7cf93d59, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2d ago.

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.

skills/bump-version/SKILL.md · 113 lines

How it starts

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

Bump Version (Sessions Chronicle)

Overview

Update release metadata consistently for this Meson + Flatpak project. Core principle: one new_version, one approved note, one successful Flatpak build.

When to Use

User asks to bump app version (0.x.y) for a release.
Version metadata must stay aligned across Cargo.toml, meson.build, src/config.rs.in, and metainfo releases.
Release notes are missing and need a generated draft before writing.

When NOT to Use

User only wants a local Rust build check (no release metadata changes).

Required Input

new_version (required): semantic version like 0.3.5.
release_notes (optional): short paragraph + bullets for metainfo.

Validation:

Reject if new_version is missing.
Reject if new_version does not match ^\d+\.\d+\.\d+$.

Quick Reference

File	Expected change
`Cargo.toml`	Set the root `[package].version = "<new_version>"`
`crates/core/Cargo.toml`	Set `[package].version = "<new_version>"`
`crates/search-provider/Cargo.toml`	Set `[package].version = "<new_version>"`
`Cargo.lock`	Update the locked versions of `sessions-chronicle`, `sessions-chronicle-core`, and `sessions-chronicle-search-provider` to match their manifests
`meson.build`	Set `project(..., version: '<new_version>', ...)`
`src/config.rs.in`	Keep `pub const VERSION: &str = @VERSION@;` (never edit `src/config.rs`)
`data/dev.maciz.sessionschronicle.metainfo.xml.in.in`	Add newest `<release version="<new_version>" date="YYYY-MM-DD">...</release>`

Implementation Workflow

Validate new_version format.
Update the [package].version in all three workspace manifests: Cargo.toml, crates/core/Cargo.toml, and crates/search-provider/Cargo.toml.
Update the corresponding three package entries in Cargo.lock; do not change dependency versions as part of the app version bump.
Update meson.build project version.
Verify src/config.rs.in still uses the @VERSION@ placeholder; never edit generated src/config.rs.
Prepare release notes for metainfo:
- If release_notes provided: use it.
- If missing: auto-generate a draft from recent commits/diff context, then ask user approval before writing.
Insert the new <release> block as the first entry under <releases>.
Verify that all three Cargo manifests, their three Cargo.lock package entries, meson.build, the config template, and the metainfo release entry are consistent. Run cargo metadata --locked --no-deps --format-version 1 to confirm lockfile consistency.
Run final Flatpak verification:

Read the full file on GitHub · 113 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.

2d ago Changed · +15 lines c9ff7cf93d59
1mo ago First seen · 98 lines · 35 tokens per session scan A 661b3773814a

Subscribe to this mod's changes

bump-version is a skill published in the GitHub repository supermaciz/sessions-chronicle (5 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,280 once invoked, about $0.0001 per session on Opus 5.5. 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-31.

Claude Code Git and workflow Releases codex-cli gnome gtk4 linux vibe-coding

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.

CherryHQ/cherry-studio · 44 tokens

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…

GCWing/BitFun · 105 tokens

bump-version