Repository navigation
INSTALLING.md and the README recording are at v0.4.1 - #27
Merged
Merged
Conversation
The step RELEASING.md gained in #26, done for the first time: INSTALLING.md's three archive examples and the pin example say 0.4.1, and docs/demo.tape downloads v0.4.1 and was re-recorded with the two commands in its header (55 s). The recording's prompt reads root@avison:<dir># instead of a bare $, so it looks like a terminal a reader recognises and shows the directory change after the clone. The downloads and the clone now Wait for the prompt instead of sleeping a fixed time: on this re-record the clone was slower and the next command was typed into its output. The tape's header says so.
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.
What changes
This is the post-release step from
RELEASING.md(#26), done for v0.4.1.INSTALLING.md: the macOS, Linux and Windows archive examples and theversion:pin example say 0.4.1.docs/demo.tape,docs/demo.gifanddocs/demo.mp4, re-recorded at v0.4.1 (55 s) with the commands in the tape's header:root@avison:<dir>#instead of a bare$.Wait) instead of sleeping a fixed time. On the first re-record the clone was slower, and the next command was typed into its output.Verified
cosign verify-blobonchecksums.txtprintsVerified OK.v0points at the release commit.sha256sum --checkprints OK,cdclint --versionprintscdclint 0.4.1, and the corpus run shows the error, the warning andexit code: 1.