# Dinky Release Bump

> Checklist for keeping Dinky release strings in sync across repo and site. Use when this capability is needed.

- Skill: `tomevault-io/dinky-release-bump` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/dinky-release-bump`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/dinky-release-bump/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/dinky-release-bump

---


# Dinky — release string bump

Use **`./release.sh X.Y.Z --bump-only`** to sync `project.pbxproj` + site URLs in one step (no build/git). Full ship: **`./release.sh X.Y.Z`** (Release build, DMG, zip, commit, tag, `gh release create`).

When shipping a new **X.Y.Z** DMG to GitHub Releases, pinned references must match:

1. **site/index.html** — `<title>`, meta descriptions, JSON-LD `downloadUrl` / `softwareVersion`, download button `href`, visible version line.
2. **site/llms.txt** — “Download v…” link.
3. **site/homepage.md** — Download bullet and version line.
4. **site/compare/\*/index.html** — DMG `href` and visible `vX.Y · Requires` line on each SEO compare page (`release.sh` updates these automatically with the homepage).
5. **README.md** — if it embeds a specific DMG URL (optional; prefer `releases/latest` in prose when possible).

Search the repo for the **previous** version number to catch stragglers.

---
> Source: [heyderekj/dinky](https://github.com/heyderekj/dinky) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-23 -->