Latest version on documentation site is behind the releases here on GitHub
See original GitHub issue- I Installed the msi linked to from the decumentation site and it is 2.012. as is here
* I ranaz --version
and get 2.0.1 - The release notes on document site stop at 2.0.6, though here on git hub the latets release is 2.0.12
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Managing releases in a repository - GitHub Docs
Creating a release · On GitHub.com, navigate to the main page of the repository. · To the right of the list of files,...
Read more >release-it/release-it: Automate versioning and ... - GitHub
Release It!. Generic CLI tool to automate versioning and package publishing related tasks: Bump version (in e.g. package.json ); Git commit, tag, push ......
Read more >release-it/github-releases.md at master
The "releases" page on GitHub projects links to a page containing the project's history, or changelog. Releases are attached to an existing Git...
Read more >GitHub Enterprise Server releases
GitHub releases new versions of GitHub Enterprise Server regularly. You can review supported versions, see deprecation dates, and browse documentation for ...
Read more >About releases - GitHub Docs
You can create a release to package software, along with release notes and links to binary files, for other people to use.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The release notes page has been updated and we’ll submit changes for future releases to the docs page.
Well, the releases listed on the documentation site are behind so I could rename issue to just cover that point if you like?