mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Link to release from version number in footer #5206
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#5206
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @benbalter on GitHub (May 16, 2024).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
I have AdGuard set to auto-update (via Watchtower). When a new version is installed, I'm often curious what's changed. Right now, I have to navigate to the GitHub repo and find the release that matches the version number in the footer of my instance.
Proposed solution
Update the version number in the footer to link to
https://github.com/AdguardTeam/AdGuardHome/releases/tag/vX.X.XwhereX.X.Xis the version number.Alternatives considered and additional information
I'd be happy to take a pass at a PR (and would be eager to make my first contribution) if someone could help point me in the right direction.
@benbalter commented on GitHub (May 16, 2024):
I'm relatively new to React, but if it's a matter of wrapping https://github.com/AdguardTeam/AdGuardHome/blob/master/client/src/components/ui/Version.js#L32 in an
<a href...I can do that, assuming there's interest in supporting this enhancement.@ainar-g commented on GitHub (May 17, 2024):
This would likely need an API extension as well, since the current HTTP API does not expose the release channel to the frontend, which is required, because development, edge, and release-candidate versions do not have their own pages.