Update deployment docs after the official AnyCable 1.0 release #267
Conversation
This file contains 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
AnyCable 1.0 has been officially released: https://evilmartians.com/chronicles/anycable-1-0-four-years-of-real-time-web-with-ruby-and-go In light of that, I've updated the docs to stop recommending installation of the release candidate version. Instead, the docs now suggest "1.0"; it didn't seem necessary to specify a patch version given that we probably don't want to have to update these docs every time a new patch version is released.
|
Thanks for this! |
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.
Type of PR: Documentation update
Description
AnyCable 1.0 has been officially released:
https://evilmartians.com/chronicles/anycable-1-0-four-years-of-real-time-web-with-ruby-and-go
In light of that, I've updated the docs to stop recommending installation of the release candidate version. Instead, the docs now suggest "1.0"; it didn't seem necessary to specify a patch version given that we probably don't want to have to update these docs every time a new patch version is released.