docs: 0.5.2 — roadmap says v0.5 shipped; extension status corrected - #24
Merged
Conversation
… real status The roadmap still listed v0.5 as planned three days after 0.5.0 shipped, because the entry was written in the same PR that implemented it and never struck through at release. The v0.6 line said 'store submission pending' when the extension has in fact been submitted to all three stores and is awaiting review.
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
1 participant
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 Roadmap on the README (and therefore the npm page) still listed
v0.5as planned three days after 0.5.0 shipped — the entry was written in the same PR that implemented it and never struck through at release time. Thev0.6line also said store submission pending when the extension has in fact been submitted to Chrome, Firefox and Whale and is awaiting review.Both languages. Version bumped to 0.5.2 so the npm page actually picks the correction up (npm renders the README from the last publish).
Checked numkey's live npm page for the same class of drift — its roadmap is current through v0.6, no change needed.
typecheck + 100 tests + build green.