القائمة
Use when cutting or preparing a new Aptos CLI release, bumping the `aptos` crate version, or editing `crates/aptos/CHANGELOG.md` for a release
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when rebasing a branch that modifies the Aptos Move framework and git reports merge conflicts in cached-packages artifacts (`head.mrb` or generated SDK builder `.rs` files under `aptos-move/framework/cached-packages/src/`). Also use when a rebase stops on a binary conflict in `head.mrb`, or when a CI job complains that "Cached framework artifacts are out-of-date" after a rebase.
Check a Move package for compilation errors
Infer specifications for a Move package
Run the Move Prover to formally verify specifications
Move development on Aptos
| name | aptos-cli-release |
| description | Use when cutting or preparing a new Aptos CLI release, bumping the `aptos` crate version, or editing `crates/aptos/CHANGELOG.md` for a release |
aptos)| File | Change |
|---|---|
crates/aptos/Cargo.toml | Set [package] version = ... to the new semver. |
crates/aptos/CHANGELOG.md | Follow Keep a Changelog and repo style: # Unreleased at top, then ## [X.Y.Z] sections newest first. |
Match the requested bump type to the version field and to how you group notes under the new ## [version] heading.
# Unreleased, collect bullet notes for changes since the last tagged CLI release (or move existing unreleased bullets).## [<new version>] immediately below # Unreleased and move the bullets for this release under it (newest release section stays directly under Unreleased).# Unreleased (for example - _No changes yet._) so the section is clearly intentional, not an oversight.After edits, run:
cargo check -p aptos
Cargo.toml without adding a matching ## [version] block (or leaving released notes only under Unreleased).crates/aptos/Cargo.toml for this workflow (not the workspace root Cargo.toml).