Why is scrutiny now in "dev" ?

[cookiemonsteruk]

Hi there. Thank you for such a useful programme.
I have been using scrutiny for some months when I switched from analogj. I was until this week on version 1.23 I think.
I came to check for updates and noticed I was quite behind, so decided to read the notes on all pages of releases looking for gotchas and only came across a requirement to backup influx db and acknowledge it with a new setting.
I backed up, and stopped + started the container (note I am old school and I am new to docker, I normally use non-docker setups).
I noticed no change. I re-read notes and thought I needed to use the new (to me) release channels/trains. So I changed the image from lates-omnibus to just latest. I noticed a change but since I saw all my graphs at the bottom disappear, I assumed a bad upgrade.

Best get to the point now.
I think the upgrade is OK now, because the functionality is there My setup is hub & spoke.
My web page now only shows "deb" without version. Is that normal? How can I verify which version I am on?
This is my compose.yaml (bar some additional comments):

include:
  - path: ../mattermost/docker/docker-compose.yml
  - path: ../mattermost/docker/docker-compose.without-nginx.yml
    env_file: ../mattermost/docker/.env

services:
  scrutiny:
    restart: unless-stopped
    container_name: scrutiny
#    image: ghcr.io/analogj/scrutiny:master-omnibus
    image: ghcr.io/starosdev/scrutiny:latest

    cap_add:
#      - SYS_RAWIO
      - SYS_ADMIN
    ports:
      - "8080:8080" # webapp
      - "8086:8086" # influxDB admin
    volumes:
      - /run/udev:/run/udev:ro
      - ./config:/opt/scrutiny/config
#      - ./config:/home/penguin/scrutiny/config/scrutiny.yaml
      - ./influxdb:/opt/scrutiny/influxdb
#    devices:
#     - "/dev/sda"
 #     - "/dev/sdb"
 #     - "/dev/sdc"
 #     - "/dev/sdf"

#    networks:
#      - notifications
#      - monitoring

    environment:
    #  notify:
    #    urls:
      - SCRUTINY_NOTIFY_URLS=mattermost://mm.mydomain.dedyn.io/x3zfc96h7brizyk9d1xy7hbgrc/opsnotify
      - SCRUTINY_INFLUXDB_29_BACKUP_CONFIRMED:YES

[Starosdev]

@cookiemonsteruk We traced this to stable-tag image publishing overlap and merged a fix into develop.

Please test the latest:

ghcr.io/starosdev/scrutiny:develop-omnibus

Then report whether UI shows correct version and whether issue is resolved. Include any remaining symptoms, image tag, and image digest.

[cookiemonsteruk]

Hi. I've done that. I don't know if that is the correct docker way but did it by docker compose down, modify the yaml, docker compose up. Maybe there's a way to just pull the new image.
Nevertheless, that has now shown pulling the image and instead of dev on the webpage, it shows 1.73.0
Thank you.
Do I need to change it again to be out of develop? I tend to prefer stable releases.

[Starosdev]

@cookiemonsteruk Thanks for testing. That confirms fix. Yes, switch back to stable when ready; develop-omnibus was only for verification.

For omnibus, change image back to:

ghcr.io/starosdev/scrutiny:latest-omnibus

Then run:

docker compose pull
docker compose up -d

docker compose pull downloads image; docker compose up -d recreates container with stable image. Existing config and InfluxDB volumes stay in place.

[cookiemonsteruk]

thanks for educating me on docker things. Done as instructed and updated, it now shows version 1.74.0
Thank you.!

[Starosdev]

Thanks for testing and confirming. Glad the stable image now shows 1.74.0. That confirms issue is fixed.

You can stay on ghcr.io/starosdev/scrutiny:latest-omnibus for future stable releases.