Garbage table registry_v031

[zc-devs]

Component

server

Describe the bug

There is unnecessary empty table registry_v031 in database.

Steps to reproduce

postgres=# \c woodpecker
You are now connected to database "woodpecker" as user "postgres".
woodpecker=# \dt
               List of relations
 Schema |       Name       | Type  |   Owner
--------+------------------+-------+------------
 public | agents           | table | woodpecker
 public | configs          | table | woodpecker
 public | crons            | table | woodpecker
 public | files            | table | woodpecker
 public | forges           | table | woodpecker
 public | log_entries      | table | woodpecker
 public | migration        | table | woodpecker
 public | orgs             | table | woodpecker
 public | perms            | table | woodpecker
 public | pipeline_configs | table | woodpecker
 public | pipelines        | table | woodpecker
 public | redirections     | table | woodpecker
 public | registries       | table | woodpecker
 public | registry_v031    | table | woodpecker
 public | repos            | table | woodpecker
 public | secrets          | table | woodpecker
 public | server_configs   | table | woodpecker
 public | steps            | table | woodpecker
 public | tasks            | table | woodpecker
 public | users            | table | woodpecker
 public | workflows        | table | woodpecker
(21 rows)

woodpecker=# select * from registry_v031;
 registry_id | registry_repo_id | registry_addr | registry_username | registry_password
-------------+------------------+---------------+-------------------+-------------------
(0 rows)

Expected behavior

There is no garbage table.

System Info

Woodpecker `2.7.0`, Postgres 16.

Additional context

#3806

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]