gitea

Author	SHA1	Message	Date
zeripath	d285905826	Update the webauthn_credential_id_sequence in Postgres (#19048 ) (#19060 ) Backport #19048 There is (yet) another problem with v210 in that Postgres will silently allow preset ID insertions ... but it will not update the sequence value. This PR simply adds a little step to the end of the v210 migration to update the sequence number. Users who have already migrated who find that they cannot insert new webauthn_credentials into the DB can either run: ```bash gitea doctor recreate-table webauthn_credential ``` or ```bash SELECT setval('webauthn_credential_id_seq', COALESCE((SELECT MAX(id)+1 FROM `webauthn_credential`), 1), false) ``` which will fix the bad sequence. Fix #19012 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: 6543 <6543@obermui.de>	2022-03-13 12:02:19 +08:00
qwerty287	054bc55a1c	Fix page and missing return on unadopted repos API (#18848 ) (#18927 ) * Fix page and missing return on unadopted repos API Page must be 1 if it's not specified and it should return after sending an internal server error. * Allow ignore pages	2022-02-27 20:18:23 +08:00
Lunny Xiao	c077a0361a	Fix migration v210 (#18893 )	2022-02-25 15:08:00 +01:00
zeripath	08d5a836ef	Attempt to fix the webauthn migration again - part 3 (#18770 ) (#18771 ) Backport #18770 v208.go is seriously broken as it misses an ID() check. We need to no-op and remigrate all of the u2f keys. See #18756 Signed-off-by: Andrew Thornton <art27@cantab.net>	2022-02-16 21:15:49 +00:00