What is release-metadata?

A release checklist for keeping version information and release notes synchronized across CHANGELOG.md, build.gradle.kts, and gradle.properties.

Use it to bump plugin versions, add dated changelog entries, update Marketplace notes, and revise the public description when features change.

It reduces the risk of publishing mismatched versions or incomplete release information in the project and on the JetBrains Marketplace.

release-metadata — Cursor rule for Cursor by vaughanb/CursorJ

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/vaughanb/CursorJ

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/vaughanb/cursorj/release-metadata/github.svg)](https://agentmods.dev/rules/vaughanb/cursorj/release-metadata)

Your own site

<a href="https://agentmods.dev/rules/vaughanb/cursorj/release-metadata"><img src="https://agentmods.dev/badge/rules/vaughanb/cursorj/release-metadata/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/vaughanb/cursorj/release-metadata"><img src="https://agentmods.dev/badge/rules/vaughanb/cursorj/release-metadata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 414 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.00000	$0.00414
Opus 5.5	$0.00000	$0.00166
Sonnet 5.5	$0.00000	$0.00083
Haiku 4.5	$0.00000	$0.00041

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

Security

Grade A, and why

release-metadata 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/release-metadata.mdc · 46 lines

What it actually says

Release Metadata

Three files must stay in sync when preparing a release:

File	What to update
`gradle.properties`	`pluginVersion`
`CHANGELOG.md`	New version section with date and categorized changes
`build.gradle.kts`	`changeNotes` (latest release highlights) and `description` (if the feature set changed)

Workflow

Bump pluginVersion in gradle.properties.
Add a new section to CHANGELOG.md following the existing Keep a Changelog format (Added, Changed, Fixed, Security).
Update changeNotes in build.gradle.kts → intellijPlatform.pluginConfiguration to match the new changelog entry as HTML.
If the release introduces or removes a user-facing feature, update description in the same block.

changeNotes format

changeNotes is an HTML string rendered on the JetBrains Marketplace "What's New" panel. Use a <h3> for the version and a <ul> for bullet points:

changeNotes = """
    <h3>X.Y.Z</h3>
    <ul>
        <li>Highlight one</li>
        <li>Highlight two</li>
    </ul>
""".trimIndent()

description format

description is an HTML string rendered on the Marketplace plugin page. Keep it concise: a one-line summary, a <ul> of key features, and links to the project home and issue tracker.

Reminders

Always update all three files together; never bump the version without updating the changelog and change notes.
See RELEASING.md for the full release checklist.

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 · 46 lines · 0 tokens per session scan A 7333616a37b4

Subscribe to this mod's changes

release-metadata is a cursor rule published in the GitHub repository vaughanb/CursorJ (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 414 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-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

release-metadata