Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Check then updat resets the 'latest' tag to a wrong value after the update #2125

Open
informagico opened this issue Jan 9, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@informagico
Copy link

Describe the bug

When images are set to latest Tag, the Check then update button will update the application but tag will be set to the wrong "numeric" value (the only other one available in my case).

This will lead to future updates to actually DOWNGRADE the application (which has happened to me this morning and I needed to restore a backup)

To Reproduce

  1. Go to container Settings > Tag and set it to latest
  2. Save
  3. Click on the three dots
  4. Check then update
  5. Alert informs you that the update is being processed asyncronously
  6. The app is updated to the latest tag
  7. Go again in the container Settings > Tag
  8. It will show now a different value (which is NOT the version I updated to)

Expected behavior

Tag should remain latest

Screenshots

Before the update (Prowlarr v1.28.2.4885 - tag latest)
image

After the update (Prowlarr v1.29.2.4915 - tag '1.9.4' which is absolutely wrong)
image

Desktop (please complete the following information):

 - OS: Debian 12
 - Browser: Firefox 134.0 (64-bit)
 - Version: CasaOS v0.4.15

System Time

Run timedatectl and share the output

               Local time: Thu 2025-01-09 18:30:25 CET
           Universal time: Thu 2025-01-09 17:30:25 UTC
                 RTC time: Thu 2025-01-09 17:30:25
                Time zone: Europe/Rome (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Logs

Run following command to collect corresponding logs:

too sensitive data, won't share
@informagico informagico added the bug Something isn't working label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant