-
Notifications
You must be signed in to change notification settings - Fork 15
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
Dynamically display ignite release versions #135
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.
I have a small Ignite PR to test with this once it's through if you like, just LMK
Looks good to me but will defer to the other reviewers!
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.
Looking good, just would remove Exp[ress]o
, other than that all comments are just ideas to consider
* Add LatestRelease component and update notificationSection styles * Fix key warning in FreshRecipes component * Fix typo in YAML heading * Added comment * Refactor recipe link key in FreshRecipes component * Update LatestVersion component title * Refactor LatestRelease component to use ReleaseRemark component * Refactor releaseString logic in LatestVersion component
* Add LatestRelease component and update notificationSection styles * Fix key warning in FreshRecipes component * Fix typo in YAML heading * Added comment * Refactor recipe link key in FreshRecipes component * Update LatestVersion component title * Refactor LatestRelease component to use ReleaseRemark component * Refactor releaseString logic in LatestVersion component
This feature dynamically displays the latest Ignite release on the homepage. It fetches release info from GitHub API, showing the version and how many days ago it was released and falls back to a generic GitHub link to `/latest/ if unable to fetch.
This approach seemed simpler than trying to implement a GH Action or using a version badge for the same info, but if we're not happy to include an API call on this site let me know :)
I also included 2 small fixes I noticed while working on this.