Project rules for semantic versioning, a release numbering system where major, minor, and patch numbers signal breaking changes, new features, and fixes. They define how changes affect version numbers and the release workflow.

Use them when reviewing changes before release, updating the changelog, choosing the next version, creating tags, and publishing releases.

They prevent inconsistent release numbers and clarify when a change requires a major, minor, or patch update.

versioning — Cursor rule for Cursor by git-treeline/cli

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.

Clone the repo

git clone --depth 1 https://github.com/git-treeline/cli

Made for: Cursor.

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/rules/git-treeline/cli/versioning/github.svg)](https://agentmods.dev/rules/git-treeline/cli/versioning)

Your own site

<a href="https://agentmods.dev/rules/git-treeline/cli/versioning"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/versioning/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/rules/git-treeline/cli/versioning"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/versioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 324 This file is loaded in full into every session.

When invoked 324 The same file — it is already loaded in full.

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.00324	$0.00324
Opus 5.5	$0.00130	$0.00130
Sonnet 5.5	$0.00065	$0.00065
Haiku 4.5	$0.00032	$0.00032

Measured 1mo ago against content hash 0fd53444fa3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

versioning 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 1mo 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.

.cursor/rules/versioning.mdc · 32 lines

What it actually says

Versioning

This project follows semver (MAJOR.MINOR.PATCH) strictly, even pre-1.0.

Bump rules

Change type	Bump	Example
Breaking API/CLI/config change	Major	Removing a command, renaming a flag, changing config schema in a non-backwards-compatible way
New feature, new CLI command/flag, new config token, new user-visible behavior	Minor	Adding `{router_domain}`, adding `X-Forwarded-Proto`, adding version tracking
Bug fix, internal refactor, docs-only, test-only	Patch	Fixing pfctl anchor ordering, fixing a typo in output

When in doubt: if a user would need to read the changelog to understand new capabilities, it's a minor bump.

Release workflow

Read and run .cursor/rules/pre-release-review.mdc against all changed files since the last tag.
Update CHANGELOG.md under a new ## [x.y.z] heading.
Commit, then git tag vx.y.z.
Push with --tags — the Release workflow handles the rest.

Batching

Multiple changes can ship in one release. The highest-severity bump wins:

2 bug fixes + 1 new feature = minor bump (not patch).
1 breaking change + 3 features = major bump.

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.

1mo ago First seen · 32 lines · 324 tokens per session scan A 0fd53444fa3b

Subscribe to this mod's changes

versioning is a cursor rule published in the GitHub repository git-treeline/cli (5 stars, last pushed 8d ago), licensed MIT. It adds 324 tokens to every session, about $0.0013 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.

Git and workflow Releases

changesets

Changeset format and bump rules enforced by CI.

adobe/spectrum-design-data · 0 tokens

release-notes

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

thatrebeccarae/claude-marketing · 50 tokens

versioning