GitLab Version - Update Version Status Indicator
What does this MR do and why?
Implements frontend for: #295266 (closed)
Part 1/2 for #254206 (closed)
Implements the Internal Endpoint added as part of !73504 (merged)
This change hooks up the above mentioned API to the GitLab frontend. Currently when showing version status of a GitLab instance we hit the /check.svg endpoint that returns a SVG. This type of endpoint doesn't allow us an easy way to hook up our GitLab UI styles or make changes very easily.
Instead with the new endpoint, we can obtain the raw version status data, then we can generate our own status indicator with GlBadge.
Screenshots or screen recordings
Status Badges
| Before | After | |
|---|---|---|
| Help Page |  |
 |
| Admin Dashboard |  |
 |
All Status Badges Variants
| Type | UI |
|---|---|
| Up to date |  |
| Update available |  |
| Update ASAP |  |
No Version Check/Non-Admin
| Location | UI |
|---|---|
| Help Page |  |
| Admin Dashboard |  |
How to set up and validate locally
Important: Since version_check uses ReactiveCaching you will need to "warm the cache up" when testing. This will mean that your first hit on your instance will be null. In the background the cache will be fetched/created async. So after reloading you should see the badge appear.
Important: You must be an Admin user to see the badge, it is worth testing that a non-admin will not see the badge any longer on the Help page.
Help Page:
- Navigate to the GitLab help page (ex.
http://127.0.0.1:3000/help) - Ensure the correct badge is displayed and the UI looks correct
Admin Dashboard:
- Navigate to the GitLab Admin Dashboard (ex.
http://127.0.0.1:3000/admin) - Scroll down to the Components card
- Ensure the correct badge is displayed and the UI looks correct
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #295266 (closed)