42.39.1

Show maintenance

September 16, 2026

Action required

The upgrade still stops if a user has an invalid handle, an invalid password hash, or a conflicting sign-in record. If this occurs, run data-migrations export legacy_identities from the internal image to see the affected users. Correct the data, then run migrate again.

Fixes

Let the database upgrade continue when users have incomplete accounts3936

The upgrade stopped if a user had a blank, malformed, or duplicate email address. Now Virtool counts these users and continues. It moves all eligible users to the new sign-in system.

42.65

42.64

42.63

42.62

42.61

42.60

42.59

42.58

42.57

42.56

42.55

42.54

42.53

42.52

42.51

42.50

42.49

42.48

42.47

42.46

42.45

42.44

42.43

42.42

42.41

42.40

42.39

42.38

42.37

42.36

42.35

42.34

42.33

42.32

42.31

42.30

42.29

42.28

42.27

42.26

42.25

42.24

42.23

42.22

42.21

42.20

42.19

42.18

42.17

42.16

42.15

42.14

42.13

42.12

42.11

42.10

42.9

42.8

42.7

42.6

42.5

42.4

42.3

42.2

42.1

42.0

42.39.1

Fixes

Let the database upgrade continue when users have incomplete accounts3936