github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-05 19:18:16 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

RC pushed to latest tag #571

New Issue
Closed
opened 2025-11-01 20:59:30 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-01 20:59:30 -05:00
Owner
Copy Link

Originally created by @RealOrangeOne on GitHub (Aug 27, 2025).

Description

I had an issue similar to #1336, but was confused as I wasn't running an unstable version. Looking at Docker Hub though, it looks like the release candidate for 1.0.0 was pushed to the latest tag.

The latest tag is what's documented as being the stable version of Vikunja to run, so it shouldn't have "candidate" (ie unstable) builds pushed to it. This means latest no longer tracks the latest "stable" version of Vikunja, as many people expect.

Vikunja Version

v1.0.0-rc1

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @RealOrangeOne on GitHub (Aug 27, 2025). ### Description I had an issue similar to #1336, but was confused as I wasn't running an unstable version. Looking at Docker Hub though, it looks like the release candidate for 1.0.0 was pushed to the `latest` tag. The `latest` tag is what's documented as being the stable version of Vikunja to run, so it shouldn't have "candidate" (ie unstable) builds pushed to it. This means `latest` no longer tracks the latest "stable" version of Vikunja, as many people expect. ### Vikunja Version v1.0.0-rc1 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:59:31 -05:00
Author
Owner
Copy Link

@RealOrangeOne commented on GitHub (Aug 27, 2025):

Rolling back to 0.24.6, the previous stable version appears to work, however there seem to have been other changes (especially around filters) which make rolling back incompatible.

@RealOrangeOne commented on GitHub (Aug 27, 2025): Rolling back to `0.24.6`, the previous stable version appears to work, however there seem to have been other changes (especially around filters) which make rolling back incompatible.
GiteaMirror commented 2025-11-01 20:59:31 -05:00
Author
Owner
Copy Link

@Millio345 commented on GitHub (Aug 27, 2025):

Same here - Can't login to Vikunja anymore after unintentionally receiving the update to an unstable version. (I was able to fix my login by updating to the new "unstable" OIDC config, but that's unrelated to this issue)

@Millio345 commented on GitHub (Aug 27, 2025): Same here - Can't login to Vikunja anymore after unintentionally receiving the update to an unstable version. (I was able to fix my login by updating to the new "unstable" OIDC config, but that's unrelated to this issue)
GiteaMirror commented 2025-11-01 20:59:31 -05:00
Author
Owner
Copy Link

@treysu commented on GitHub (Aug 28, 2025):

@RealOrangeOne Same here, I was able to rollback and get most things up and running. However, I am getting lots of errors it seems. Excited for 1.0 but I would've certainly done a proper backup if I was going to update to a release candidate intentionally.

@treysu commented on GitHub (Aug 28, 2025): @RealOrangeOne Same here, I was able to rollback and get most things up and running. However, I am getting lots of errors it seems. Excited for 1.0 but I would've certainly done a proper backup if I was going to update to a release candidate intentionally.
GiteaMirror commented 2025-11-01 20:59:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 29, 2025):

Unfortunately, we can't switch the tag back since users already upgraded and rolling back is not supported (as you noticed). This is definitely a bug in the release pipeline - I'll take care of it so that it won't happen again, but that's only for future major version releases, later than 1.0.

The way to roll back is to restore from the backup you did before upgrading (you did a backup before upgrading, right?).

@kolaente commented on GitHub (Aug 29, 2025): Unfortunately, we can't switch the tag back since users already upgraded and rolling back is not supported (as you noticed). This is definitely a bug in the release pipeline - I'll take care of it so that it won't happen again, but that's only for future major version releases, later than 1.0. The way to roll back is to restore from the backup you did before upgrading (you did a backup before upgrading, right?).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#571
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?