Repository navigation
Say which version this is - #2
Merged
Merged
Conversation
The README never named one, because it was written before this repository had a tag. A reader deciding whether to implement SIGNING.md needs to know which release the document they are reading belongs to. States v0.1.0 once, at the top, and the thing that actually makes it meaningful: the core and the agent both build against it with no replace directive, which is the only real test of whether this was published or merely copied.
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.
The README never named a version, because it was written before this repository had a tag. A reader deciding whether to implement
SIGNING.mdneeds to know which release the document they are reading belongs to.States
v0.1.0once, at the top — and the thing that actually makes it meaningful: the core and the agent both build against it with noreplacedirective, which is the only real test of whether this was published or merely copied.Part of a documentation resync across all six repositories after the split and the v0.1.1 release.