Title: Expose the running Feast version in the UI · Issue #6842 · feast-dev/feast · GitHub
Open Graph Title: Expose the running Feast version in the UI · Issue #6842 · feast-dev/feast
X Title: Expose the running Feast version in the UI · Issue #6842 · feast-dev/feast
Description: What is the problem? The Feast UI does not show which Feast package version the running service is using. The UI server health endpoint returns status only, so operators need container or cluster access to verify a deployed release. Prop...
Open Graph Description: What is the problem? The Feast UI does not show which Feast package version the running service is using. The UI server health endpoint returns status only, so operators need container or cluster a...
X Description: What is the problem? The Feast UI does not show which Feast package version the running service is using. The UI server health endpoint returns status only, so operators need container or cluster a...
Opengraph URL: https://github.com/feast-dev/feast/issues/6842
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Expose the running Feast version in the UI","articleBody":"### What is the problem?\n\nThe Feast UI does not show which Feast package version the running service is using. The UI server health endpoint returns status only, so operators need container or cluster access to verify a deployed release.\n\n### Proposed behavior\n\nAdd an authenticated `GET /api/v1/version` endpoint to the shared registry REST API and show its result in the UI sidebar. The response should be derived from `feast.version.get_version()` in the running process, for example:\n\n```json\n{\"feast_version\": \"0.66.0\"}\n```\n\nThe UI should hide the label without disrupting navigation when the endpoint is unavailable, preserving compatibility with older or custom backends. The existing health endpoint should remain unchanged.\n\n### Why use the shared REST API?\n\nBoth the UI-mounted API and standalone registry REST server register the same router set and apply authentication at the application level. A shared route provides one contract without duplicating authentication or server-specific code.\n\n### Acceptance criteria\n\n- The value comes from installed package metadata in the running Python process.\n- Existing REST authentication applies to the endpoint.\n- The UI displays the version in its sidebar when available.\n- Missing or failed version requests are nonfatal.\n- Health endpoint behavior remains unchanged.","author":{"url":"https://github.com/larrysingleton007","@type":"Person","name":"larrysingleton007"},"datePublished":"2026-09-17T14:30:58Z","url":"https://github.com/feast-dev/feast/issues/6842"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:52df1b03-d9d2-5447-874a-649b880403d5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D91A:F21AC:2AF12F:3BA93E:6AFE9815 |
| html-safe-nonce | bc35d32dfd91de21a5e4fcddf22a0d1babad1c1ed5c15a7b083f2e6cdac09cd0 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEOTFBOkYyMUFDOjJBRjEyRjozQkE5M0U6NkFGRTk4MTUiLCJ2aXNpdG9yX2lkIjoiODkzMjMwODQ4NjI5NzA4ODIxIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 770efb2e1c3454fef4b47a2b353d2e60a3027ed4d907ef586b4862793683b947 |
| hovercard-subject-tag | issue:5488774924 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/6842/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2d9479391f8756a1217c3e13e1119ad00e18396508337af62b57d14852a271bd/feast-dev/feast/issues/6842 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2d9479391f8756a1217c3e13e1119ad00e18396508337af62b57d14852a271bd/feast-dev/feast/issues/6842 |
| og:image:alt | What is the problem? The Feast UI does not show which Feast package version the running service is using. The UI server health endpoint returns status only, so operators need container or cluster a... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | larrysingleton007 |
| hostname | github.com |
| expected-hostname | github.com |
| None | b3c0f155eafc27e60db6e254d1ffff0e072e9ab3b4018a5ee518797c19d89f86 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a10310af51a1bfffbedc4fd81cb582acf0cb0ff |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width