docs: install from the release, and start a changelog - #2
Merged
Conversation
Two consequences of having a first release. The quickstart still opened with `go build -o stone`, so the six prebuilt archives now attached to v0.1.0 were invisible and every user compiled their own; it now downloads one and mentions the full target list, keeping the build-it-yourself line as the alternative it now is. And there was no changelog, so "what changed since v0.1.0" had no answer beyond commit subjects. Seeded with the state at first tag, in the same format the platform repo uses, including the two caveats a reader needs: the field list is hand-maintained and can lag a platform release, and `auth login` is interactive on purpose. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two chores created by cutting v0.1.0.
The quickstart still said
go build -o stone. Six prebuilt archives are attached to the release and nothing pointed at them, so every user compiled their own and--versionreporteddev. Step 1 now downloads one, names the full target list (linux/darwin/windows × amd64/arm64), and keeps the source build as the alternative it now is. The subsequent steps still use./stone, which stays correct — the archive unpacks the binary into the working directory.No
CHANGELOG.md, so "what changed since v0.1.0" had no answer beyond commit subjects. Seeded with the state at first tag in the same Keep a Changelog format the platform repo uses, including the two caveats a reader actually needs: the field list is hand-maintained and can lag a platform release, andauth loginis interactive on purpose.The docs site gets the matching change in stone-age-io/platform-docs.
🤖 Generated with Claude Code