Torsten Grote fa65084e60 [db] make repo certs non-null and remove repos without cert ...

historically, repos were added to the DB without much information and could stay in a broken state until manually removed. If a repo is updating, it should have a cert. So only repos that never did a single index update don't have a cert. Nowadays, this can not happen anymore as we get the repo and its cert before adding it to the DB. So whenever we update a repo, we know its certificate and fingerprint. Thus, this includes a DB migration removing all broken repos and making the certificate for repos in the DB non-null.

2024-05-22 09:58:05 +00:00

..

1.json

Update Room DB schema to match actual schema used

2022-12-15 17:10:08 +00:00

2.json

[db] Only consider preferred versions for updates and suggested version

2024-02-20 09:42:39 -03:00

3.json

[db] make repo certs non-null and remove repos without cert

2024-05-22 09:58:05 +00:00

4.json

[db] make repo certs non-null and remove repos without cert

2024-05-22 09:58:05 +00:00