forgejo/models/migrations
Gergely Nagy 8fdffc94ca Add a migration to remove SSH signatures from release notes
Because the `git` module did not recognize SSH signed tags, those
signatures ended up in the `notes` column of the `release` table. While
future signatures will not end up there, Forgejo should clean up the old
ones.

This migration does just that: finds all releases that have an SSH
signature, and removes those signatures, preserving the rest of the
note (if any).

While this may seem like an expensive operation, it's only done once,
and even on the largest known Forgejo instance as of this
writing (Codeberg), the number of affected rows are just over a hundred,
a tiny amount all things considered.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
2024-03-26 08:09:36 +00:00
..
base fail test when log.Error is called 2024-03-24 07:11:18 +01:00
fixtures Add a migration to remove SSH signatures from release notes 2024-03-26 08:09:36 +00:00
v1_6
v1_7
v1_8
v1_9
v1_10
v1_11 migration v1_11/v111.go: Unknown columns in 'field list' 2024-03-24 07:12:31 +01:00
v1_12 old migrations: warning instead of error 2024-03-24 07:11:19 +01:00
v1_13
v1_14 [GITEA] Drop sha256-simd in favor of stdlib 2024-02-05 16:09:40 +01:00
v1_15
v1_16 Fix bug hidden on CI and make ci failed if tests failure (#29254) 2024-03-11 23:36:59 +07:00
v1_17
v1_18 Refactor system setting (#27000) 2023-10-05 09:08:19 +08:00
v1_19
v1_20
v1_21 [GITEA] new doctor check: fix-push-mirrors-without-git-remote (#1853) 2024-02-05 16:09:41 +01:00
v1_22 add test for webhook migration 2024-03-11 23:37:00 +07:00
migrations.go Store webhook event in database (#29145) 2024-03-11 23:36:59 +07:00