docs: point the immutable install pins at v0.10.2 - #190
Merged
Conversation
The commit-pinned examples still named the v0.10.1 release commit, and the Cursor and Copilot guides labelled it `# v0.10.1` directly beneath install instructions that now say v0.10.2. docs/demo-prs.md keeps the v0.9.0 SHA. That line is not an install instruction; it records which pinned build produced three verified external runs, and changing it would misstate what was executed.
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
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.
Follow-up to v0.10.2. The commit-pinned examples still named the v0.10.1 release
commit, and in the Cursor and Copilot guides it was labelled
# v0.10.1rightunder install instructions that now say v0.10.2.
Now
415122bf756157735b5b2e569c48a846064f5b17, which is what thev0.10.2tagpoints at, and which is the exact ref the sandbox used to produce
this run.
docs/demo-prs.mddeliberately keeps its older SHA: that line records whichpinned build produced three verified external runs, not what to install.