-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): bump version number in docs example #27038
chore(docs): bump version number in docs example #27038
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Is there an easy way in docausurus "templatize" and use a variable like This look promising -> facebook/docusaurus#5700 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting to "Request changes" as otherwise it'll get stale or force us to grep + multi-update at every release... This also sets a new pattern to keep the docs more dynamic, worth doing if we can figure this out quickly.
I'm fine with letting this through and following up on a fancier version. For getting fancy, we need to differentiate between latest stable (i.e. not a major x.0.0) and latest, so doing it as part of the release process might not work the way we want. We could make a little script as a "prebuild" step for docusaurus, so that whenever it builds, it scrapes GitHub (or Apache, potentially) for all the latest releases, and saves a little JSON object like :
This could then be directly included in any MDX page to spit out whatever we want, perhaps via a React component like |
Ok it's getting too fancy, do whatevs :) |
We have a task board for Documentation. I'll put this idea on there for a rainy day :) |
SUMMARY
There are example version numbers in the Alerts & Reports docs listed as 2.0.1. At least one new user took this as a sign that this page was stale. It is not. I am bumping it to 3.1.0 to make that clearer.
ADDITIONAL INFORMATION