OpenParable
Skip to content
← Back to skills

Aptos CLI Release

Development
aptos-cli-release

Aptos CLI Release is an Agent Skill for development published in the aptos-labs/aptos-core repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when cutting or preparing a new Aptos CLI release, bumping the `aptos` crate version, or editing `crates/aptos/CHANGELOG.md` for a release

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/aptos-labs/aptos-core/blob/HEAD/.cursor/skills/aptos-cli-release/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/aptos-cli-release, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Aptos CLI release (crate aptos)

Files

FileChange
crates/aptos/Cargo.tomlSet [package] version = ... to the new semver.
crates/aptos/CHANGELOG.mdFollow Keep a Changelog and repo style: # Unreleased at top, then ## [X.Y.Z] sections newest first.

Versioning

  • Patch (9.1.0 → 9.1.1): bugfixes only.
  • Minor (9.1.0 → 9.2.0): new features or non-breaking additions.
  • Major (9.x → 10.0.0): breaking CLI or documented compatibility breaks.

Match the requested bump type to the version field and to how you group notes under the new ## [version] heading.

Changelog workflow

  1. Under # Unreleased, collect bullet notes for changes since the last tagged CLI release (or move existing unreleased bullets).
  2. When releasing, add ## [<new version>] immediately below # Unreleased and move the bullets for this release under it (newest release section stays directly under Unreleased).
  3. If nothing is pending after a release, keep one placeholder bullet under # Unreleased (for example - _No changes yet._) so the section is clearly intentional, not an oversight.

Verification

After edits, run:

cargo check -p aptos

Common mistakes

  • Bumping Cargo.toml without adding a matching ## [version] block (or leaving released notes only under Unreleased).
  • Forgetting that the CLI version lives only in crates/aptos/Cargo.toml for this workflow (not the workspace root Cargo.toml).