How do I install the Release skill?

Run npx skillmds@latest add solana-foundation/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

solana-foundation (@solana-foundation) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by solana-foundation — Agent Skill

Name: Release
Author: solana-foundation

Release

Prepare a Kora release PR. Bumps Rust crate versions (kora-lib + kora-cli), optionally bumps the TypeScript SDK, generates CHANGELOG, and opens a PR against main. Use when the user says 'prepare a release', 'cut a release', or 'release version X.Y.Z'.

solana-foundation ede9bc0 2 files · 4.1 KB Updated Sep 17, 2026

File contents

Kora Release Preparation

Bump versions, generate the CHANGELOG, open a PR against main. Publishing happens after merge via CI — see the complete-release skill.

Decide first

Read current versions, then ask the user which components to release and at what versions:

cargo metadata --no-deps --format-version 1 | jq -r '.packages[] | select(.name=="kora-lib") | .version'
node -p "require('./sdks/ts/package.json').version"

Rust and TypeScript release independently. Prereleases use semver suffixes (2.3.0-beta.1).

Work on a chore/release-v${VERSION} branch off main with a clean tree.

Bump only kora-lib and kora-cli

Do not run cargo set-version --workspace. The workspace also contains crates/kora-deploy (published separately, currently on its own 0.x line) and examples/devnet-deploy-paymaster. A workspace-wide bump drags both onto the Kora version and kora-deploy has no publish = false to stop it reaching crates.io.

Four places move together, and kora-lib + kora-cli always share one version:

cargo set-version -p kora-lib -p kora-cli "${RUST_VERSION}"

Then edit by hand in the root Cargo.toml:

[workspace.package] version — tests inherits this
the kora-lib = { path = "crates/lib", version = "..." } pin in [workspace.dependencies]

Confirm nothing else moved before committing:

git diff --stat
grep -rn '^version' crates/*/Cargo.toml Cargo.toml

crates/kora-deploy/Cargo.toml must be untouched.

CHANGELOG

git-cliff appends rather than regenerates, and the invocation differs depending on whether a previous tag and CHANGELOG exist. See references/changelog.md.

TypeScript

npm version "${TS_VERSION}" --no-git-tag-version --prefix sdks/ts

Commit and PR

Commit message: chore: release v${RUST_VERSION}, plus rust + ts-sdk v${TS_VERSION} when both move. PR targets main, reviewers dev-jodee,amilz. Body should list the crates and versions being released and point at the complete-release skill for publishing.

Constraints

Release PRs always target main, regardless of the current branch.
Hotfix patches publish from hotfix/* before merge-back to main.
Never call just release or just release-ts-sdk — both are interactive and will hang.
Tags (v{VERSION}, kora-lib-v{VERSION}, kora-cli-v{VERSION}) are created by CI after merge, not here.

---name: releasedescription: Prepare a Kora release PR. Bumps Rust crate versions (kora-lib + kora-cli), optionally bumps the TypeScript SDK, generates CHANGELOG, and opens a PR against main. Use when the user says 'prepare a release', 'cut a release', or 'release version X.Y.Z'.---# Kora Release PreparationBump versions, generate the CHANGELOG, open a PR against `main`. Publishing happens after mergevia CI — see the `complete-release` skill.## Decide firstRead current versions, then ask the user which components to release and at what versions:```bashcargo metadata --no-deps --format-version 1 | jq -r '.packages[] | select(.name=="kora-lib") | .version'node -p "require('./sdks/ts/package.json').version"```Rust and TypeScript release independently. Prereleases use semver suffixes (`2.3.0-beta.1`).Work on a `chore/release-v${VERSION}` branch off `main` with a clean tree.## Bump only kora-lib and kora-cli**Do not run `cargo set-version --workspace`.** The workspace also contains `crates/kora-deploy`(published separately, currently on its own `0.x` line) and `examples/devnet-deploy-paymaster`.A workspace-wide bump drags both onto the Kora version and `kora-deploy` has no `publish = false`to stop it reaching crates.io.Four places move together, and `kora-lib` + `kora-cli` always share one version:```bashcargo set-version -p kora-lib -p kora-cli "${RUST_VERSION}"```Then edit by hand in the root `Cargo.toml`:- `[workspace.package] version` — `tests` inherits this- the `kora-lib = { path = "crates/lib", version = "..." }` pin in `[workspace.dependencies]`Confirm nothing else moved before committing:```bashgit diff --statgrep -rn '^version' crates/*/Cargo.toml Cargo.toml````crates/kora-deploy/Cargo.toml` must be untouched.## CHANGELOGgit-cliff appends rather than regenerates, and the invocation differs depending on whether aprevious tag and CHANGELOG exist. See [references/changelog.md](references/changelog.md).## TypeScript```bashnpm version "${TS_VERSION}" --no-git-tag-version --prefix sdks/ts```## Commit and PRCommit message: `chore: release v${RUST_VERSION}`, plus ` rust + ts-sdk v${TS_VERSION}` when bothmove. PR targets `main`, reviewers `dev-jodee,amilz`. Body should list the crates and versionsbeing released and point at the `complete-release` skill for publishing.## Constraints- Release PRs always target `main`, regardless of the current branch.- Hotfix patches publish from `hotfix/*` *before* merge-back to `main`.- Never call `just release` or `just release-ts-sdk` — both are interactive and will hang.- Tags (`v{VERSION}`, `kora-lib-v{VERSION}`, `kora-cli-v{VERSION}`) are created by CI after merge, not here.

Frequently asked questions