Repository navigation
Show the app version in the site footer - #1868
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 16 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1868 +/- ##
==========================================
- Coverage 43.41% 43.35% -0.06%
==========================================
Files 282 282
Lines 7267 7277 +10
Branches 1459 1464 +5
==========================================
Hits 3155 3155
- Misses 4091 4101 +10
Partials 21 21
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
The site footer now shows which version is running, next to the copyright line, like Backstage does. Tagged builds show
v1.5.0and link to that GitHub release; builds frommainshow the short commit hash and link to the commit. Local dev and tests show nothing.The link opens in a new tab with the same arrow as the footer's other external links, and screen readers read it as "Verzió: v1.5.0".
How the version gets there
No workflow or Dockerfile change. The image build already passes
SENTRY_RELEASE(request-manager@<version>on tags, the commit SHA otherwise) for the Sentry plugin. Vite now also exposes it to the app asimport.meta.env.RELEASE, and the footer turns it back into a release or commit link.Notes for reviewers
docker-publish.yml: therequest-manager@prefix, and thevthat the workflow strips and the footer adds back. If that naming changes, the link breaks without any build error.