Repository navigation
docs: keep versions 0.x until muster 1.0 and sync the protocol copy - #8
Merged
Merged
Conversation
alexmorbo
changed the title
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 library is released as 0.x until Muster 1.0, and protocol version 1 does not depend on the library version.
Also syncs api/bridge.yaml and the generated models with muster master (muster PR #301 reworded the max buttons description).
Part of muster-io/muster#240
Story: None (docs wording, decision D395)
Acceptance evidence
None: wording change only.
verifyoutputNot run: docs-only change.
Story file changed in muster-io/muster: why
None.
Dependencies
None added.
Maintainer steps
None.