tl-vikunja

History

fix(migration): make sure to correctly check if a migration was already running

This change fixes a bug where Vikunja would not correctly check if a migration was already running. That meant it was not possible for users who had never before migrated anything to start a migration, because Vikunja assumed they already had a migration running for them.
This state was neither properly reflected in the frontend, which is now fixed as well.

2024-02-13 22:21:59 +01:00

common.go

chore: remove year from copyright headers

2023-09-01 08:32:28 +02:00

events.go

feat(migration): migration from other services now happens in the background

2023-11-09 00:15:11 +01:00

handler_file.go

feat(migration): migration from other services now happens in the background

2023-11-09 00:15:11 +01:00

handler.go

fix(migration): make sure to correctly check if a migration was already running