What is making-a-release?

A release procedure for fused-render that updates its version, merges the change through a pull request, and creates a matching Git tag. The tag starts the workflow that builds, signs, notarizes, and publishes the macOS disk image.

Bumping the version, opening the required pull request, tagging the merged commit, and triggering the release workflow.

It prevents releases from bypassing the protected main branch, using the wrong version source, or creating a tag that does not match the shipped version.

making-a-release — Skill for Claude Code and Codex by fusedio: A release procedure for fused-render that updates its version…

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/fusedio/fused-render/making-a-release

Any agent

npx skills add fusedio/fused-render --skill making-a-release

Clone the repo

git clone --depth 1 https://github.com/fusedio/fused-render

Made for: Claude Code, Codex.

Or install fused-render, the plugin that ships this one along with the rest of its 15 skills.

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/fusedio/fused-render/making-a-release.svg)](https://agentmods.dev/skills/fusedio/fused-render/making-a-release)

Your own site

<a href="https://agentmods.dev/skills/fusedio/fused-render/making-a-release"><img src="https://agentmods.dev/badge/skills/fusedio/fused-render/making-a-release.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,437 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.

Model	Per session	Once invoked
Fable 5	$0.00058	$0.01437
Opus 5	$0.00029	$0.00718
Sonnet 5	$0.00012	$0.00287
Haiku 4.5	$0.00006	$0.00144

Measured 5d ago against content hash fa4406ebe455, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

making-a-release 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 5d 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.

.claude/skills/making-a-release/SKILL.md · 115 lines

How it starts

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

Making a Release

Overview

A release is: bump __version__, land that bump on main through a PR, then tag the merged commit vX.Y.Z and push the tag. Pushing the tag is what triggers .github/workflows/release.yml (build → sign → notarize → publish DMG + GitHub Release).

main is a protected branch. Direct pushes are rejected (GH006: Changes must be made through a pull request), so the bump PR is not optional — it is the only path. Do not try git push origin main first.

Single source of truth: the version lives ONLY in fused_render/__init__.py. pyproject.toml derives it dynamically ([tool.hatch.version]) — never edit a version into pyproject.toml.

The invariant that matters: the git tag name must equal __version__. Tag v0.3.5 ⟺ __version__ = "0.3.5". A mismatch ships the wrong version silently.

Steps

Start clean and on the latest main. Always pull first — tagging a stale commit ships an old build. Use --ff-only so a diverged local branch errors out loudly instead of creating a merge commit:
```
git switch main
git pull --ff-only origin main   # REQUIRED: get the latest before releasing
git status --porcelain
```
If git pull --ff-only fails, your local main has diverged — reconcile it before continuing. If git status --porcelain prints anything, stop and resolve it first.
Pick the new version. Read the current value and the latest tag; choose the next semver:
```
grep __version__ fused_render/__init__.py
git tag --sort=-creatordate | head -1
```
Branch, then bump. Work on a branch from the start — main is protected:
```
git switch -c bump-X.Y.Z
```
Bump __version__ in fused_render/__init__.py (Edit tool). This is the only file to change.
Commit (message matches the repo's history convention exactly):
```
git commit -am "Bump version to X.Y.Z"
```
Open the bump PR and let it merge. Push the branch and open the PR with the creating-pull-requests skill (title Bump version to X.Y.Z), then enable auto-merge so it lands as soon as checks go green:
```
git push -u origin HEAD
gh pr create --title "Bump version to X.Y.Z" --body-file <body.md>
gh pr merge <N> --squash --auto
```
Poll until it actually reports MERGED — do NOT tag before then:
```
gh pr view <N> --json state,mergeStateStatus,mergeCommit
```

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

5d ago First seen · 115 lines · 58 tokens per session scan A fa4406ebe455

Subscribe to this mod's changes

making-a-release is a skill published in the GitHub repository fusedio/fused-render (11 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,437 once invoked, about $0.0003 per session on Opus 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-30.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens