Repository navigation
docs(playground): say that the Dockerfile stack needs repokeeper 0.9.0 - #67
Merged
Merged
Conversation
The page names the first repokeeper that knows the standard, 0.8.2, and adds a note for the two switches that came later. The Dockerfile stack came with 0.9.0 too and had no note, so the page offered a file that 0.8.2 refuses.
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 playground ends with "Needs repokeeper 0.8.2 or newer": the first release that knows the standard the file names. The two switches that came later (update pull requests, code scanning) each add a note saying they need 0.9.0. The Dockerfile stack also came with 0.9.0 and had no note, so with it ticked the page offered a file that repokeeper 0.8.2 refuses.
Ticking Dockerfile now adds "The Dockerfile stack needs repokeeper 0.9.0 or newer.", on GitHub and on GitLab.
The playground is not part of the npm package, so this is a
docschange and asks for no release.Checked