docs: sha256:69ae50e537d929ac0661cd4da7f3e58719b13f80a1f799b072e874cd5ab6383e · gabriel/musehub

docs: lock in sequential auto-increment for nightly numbering

Decided after comparing sequential vs date-based vs Unix-timestamp numbering: sequential (dev1, dev2, ...), starting fresh at dev1 rather than continuing from rc16.

- Date-based collides under this workspace's actual cadence — one session produced 5 separate meaningful CLI publishes in a single day. - A Unix timestamp is provably collision-free but unreadable, and like the date option still can't answer "how many nightlies so far" the way a sequential count does. - committed_at already records "when" precisely on every commit — encoding a coarser copy of that in the version number is redundant. - Starting at dev1 (not dev17) avoids implying 16 prior builds existed under a name (nightly) they were never actually tracked as.

Updated all examples in versioning.md and deploy.md to dev1 for consistency.

symbol added

~16

symbols modified

files changed

1006

files in snapshot

dead code introduced

Semantic Changes 17 symbols

~ docs/deploy.md .md 8 symbols modified

~ code[bash]@L48

~ code[bash]@L55

~ code[bash]@L71

~ code[bash]@L112

~ code[bash]@L96

~ Deploy Runbook

~ Standard release flow

~ code[bash]

~ docs/versioning.md .md 1 symbol added, 8 symbols modified

+ Nightly numbering — decided: sequential auto-increment, reset to 1 section Nightly numbering — decided: sequential auto-increment, reset to 1 L158–193

~ 0, and Build Channels

~ Decision table — which format, when

~ table

~ The four build channels

~ Nightly — earliest, continuous

~ The pivot to nightly

~ Translating between the two for the same release

~ table

Files Changed

1006 in snapshot

~ docs/deploy.md .md

~ docs/versioning.md .md

← Older Oldest on docs/nightly-numbering-decision

All commits

Newer → Latest on docs/nightly-numbering-decision

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:69ae50e537d929ac0661cd4da7f3e58719b13f80a1f799b072e874cd5ab6383e --body "your comment"