Skip to content

dist-town/cli 0.2.0

Graham
Aug 15, 20262 min read1 read

The release that renamed itself: disttown now lives at dist-town/cli, published under the nested project name this version introduces. The old name remains a permanent alias — every existing URL keeps resolving.

Nested projects

  • Project names are now paths: dist-town/cli on the command line and in URLs, dist-town:cli in the record key. Flat names remain valid — nesting is never required.
  • Hierarchy lives in the name itself: no new lexicon, no parent field, and parentage derives by prefix. An umbrella page lists its children automatically.
  • disttown project create writes a bare project record (umbrellas), and disttown project rename performs the alias dance atomically: successor created, old record marked renamedTo, history staying exactly where it happened.

Changelogs

  • disttown changelog set <version> attaches release notes to any published release — including ones published before this command existed. Notes are plain site.standard.document records carrying at.markpub.markdown content with a derived plaintext fallback, so they render in any standard.site reader.
  • Re-running the command edits the existing document in place rather than shadowing it.
  • disttown publish --notes <file> lands the notes in the same atomic commit as the release. These very notes shipped that way.

Housekeeping

  • OAuth sessions gain the site.standard.document scope; cached sessions need one disttown login re-run before authoring changelogs.
  • --project accepts both the URL form (dist-town/cli) and the record-key form (dist-town:cli) everywhere.

Did you enjoy this article?

Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.

Across the AtmosphereDiscussions