-
-
Notifications
You must be signed in to change notification settings - Fork 287
Scrutiny releases do not consistently show the correct version #998
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingbuildsIssues that require updating the build process, docker images, etc.Issues that require updating the build process, docker images, etc.contributor friendlyA well-scoped, approachable issue for someone looking to contribute.A well-scoped, approachable issue for someone looking to contribute.
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingbuildsIssues that require updating the build process, docker images, etc.Issues that require updating the build process, docker images, etc.contributor friendlyA well-scoped, approachable issue for someone looking to contribute.A well-scoped, approachable issue for someone looking to contribute.
Discussed in #993
Originally posted by soloam April 24, 2026
Issue Description
This is a small "erro", but even qhen downloading a released version, the version printed is the master#<> and not the actual version
Expected Behavior
If I download a release version I would like to see the version so that I can see if I need to update
Actual Behavior
If I download a release version I would like to see the version so that I can see if I need to update
Reproduction Steps
scrutiny debug logs
No response
Scrutiny Version
v0.9.1
Smartmontools Version
7.2
OS Version Information
Debian 13
Component
web
Deployment Method
Hard Drive Information
No response
smartctl output
No response
docker-compose.yml
No response
scrutiny.yaml
No response
collector.yaml
No response
Additional relevant configuration
No response
I acknowledge that:
```) on separate lines.