@sacho/sacho-aarch64-unknown-linux-musl 0.1.0-dev.12 → 0.1.0-dev.14

package/README.md

@@ -1,6 +1,27 @@
 Sacho: an opinionated changelog manager
 =======================================
 
+[![GitHub Releases][GitHub Releases badge]][GitHub Releases]
+[![crates.io][crates.io badge]][crates.io]
+[![npm][npm badge]][npm]
+[![GitHub Actions][GitHub Actions badge]][GitHub Actions]
+[![License: GPL-3.0-only][GPL-3.0 badge]][GPL-3.0]
+[![GitHub Sponsors][GitHub Sponsors badge]][GitHub Sponsors]
+
+[GitHub Releases badge]: https://img.shields.io/github/v/release/dahlia/sacho?logo=github
+[GitHub Releases]: https://github.com/dahlia/sacho/releases
+[crates.io badge]: https://img.shields.io/crates/v/sacho?logo=rust
+[crates.io]: https://crates.io/crates/sacho
+[npm badge]: https://img.shields.io/npm/v/@sacho/sacho?logo=npm
+[npm]: https://www.npmjs.com/package/@sacho/sacho
+[GitHub Actions badge]: https://github.com/dahlia/sacho/actions/workflows/main.yaml/badge.svg
+[GitHub Actions]: https://github.com/dahlia/sacho/actions/workflows/main.yaml
+[GPL-3.0 badge]: https://img.shields.io/github/license/dahlia/sacho
+[GPL-3.0]: https://www.gnu.org/licenses/gpl-3.0.html
+[GitHub Sponsors badge]: https://img.shields.io/github/sponsors/dahlia?logo=githubsponsors
+[GitHub Sponsors]: https://github.com/sponsors/dahlia
+
+
 Motivation
 ----------
 
@@ -52,7 +73,6 @@ Without mise, npm, or Cargo, download the archive for your platform from
 *sacho* (*sacho.exe* on Windows) into a directory on your `PATH`.
 
 [mise]: https://mise.jdx.dev/
-[GitHub Releases]: https://github.com/dahlia/sacho/releases
 
 
 Agent Skill
@@ -173,10 +193,10 @@ staged Git changes or `sacho check --base <revision>` in CI.
 
 When the version is ready, compile and consume its fragments. This command
 releases the version stored by `sacho next`, uses the current local date, and
-starts the next version:
+closes the materialized unreleased region:
 
 ~~~~ sh
-sacho release --next 1.3.0
+sacho release
 ~~~~
 
 If no next version has been set, pass the release version explicitly, for
@@ -185,6 +205,16 @@ must be supplied rather than taken from the local clock. A repository with no
 released changelog sections can cut its first release without fragments. Later
 empty releases require an explicit `--allow-empty`.
 
+Commit and tag that released-only state. When development resumes, start the
+next cycle separately:
+
+~~~~ sh
+sacho next 1.3.0
+~~~~
+
+Pass `--next 1.3.0` to `sacho release` only when the release commit should also
+open the next cycle and retain its empty materialized region.
+
 After committing a release, print its frozen Markdown section with `show`:
 
 ~~~~ sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sacho/sacho-aarch64-unknown-linux-musl",
-  "version": "0.1.0-dev.12+df65120",
+  "version": "0.1.0-dev.14+4b1514b",
   "description": "The Sacho binary for aarch64-unknown-linux-musl",
   "license": "GPL-3.0-only",
   "author": "Hong Minhee <hong@minhee.org>",