forgejo

Author	SHA1	Message	Date
zeripath	886b1de949	Update the webauthn_credential_id_sequence in Postgres (#19048 ) * Update the webauthn_credential_id_sequence in Postgres 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 ./gitea doctor --run=check-db-consistency --fix ``` which will fix the bad sequence. Fix #19012 Signed-off-by: Andrew Thornton <art27@cantab.net>	2022-03-10 23:04:55 +01:00
Lunny Xiao	a5e8daee73	Fix migration v210 (#18892 )	2022-02-25 15:04:59 +01:00
silverwind	2b9df564b8	Lock gofumpt to v0.3.0 and run it (#18866 ) We can't depend on `latest` version of gofumpt because the output will not be stable across versions. Lock it down to the latest version released yesterday and run it again.	2022-02-23 20:16:07 +00:00
zeripath	3a29a23cdc	Attempt to fix the webauthn migration again - part 3 (#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:03:58 +00:00