Closed rikinsk closed 2 months ago
The PR effectively comments out the hard-coded version and notes the intended future change to fetch the version dynamically. However, the commented out TODO should include specific guidance or a ticket reference for implementation to ensure it doesn't get overlooked.
While the PR removes the hard-coded version information, it doesn't yet implement the dynamic fetching of the latest version. This leaves the usability of the documentation lacking, as users are now not informed about the latest version at all. Completing the TODO to fetch the version data dynamically should resolve this.
Description
Remove latest CLI version from the Install CLI component.
Why?
How should we re-add it?
https://graphql-engine-cdn.hasura.io/ddn/cli/<revision>/latest.json
e.g. https://graphql-engine-cdn.hasura.io/ddn/cli/v4/latest.json, https://graphql-engine-cdn.hasura.io/ddn/cli/v3/latest.json etc.Quick Links 🚀
🤖 DX: Assertion Tests
Avoid showing a hardcoded CLI latest version which can go out of date