fix: add content_type column to multipart_uploads migration
Deploy FileDrop / deploy (push) Successful in 50s
Deploy FileDrop / deploy (push) Successful in 50s
The createMultipartUpload function inserts content_type but the database column was missing, causing 500 errors on every Gitea Docker registry push (which uses multipart uploads for blob storage). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
+2
-1
@@ -56,7 +56,8 @@ CREATE TABLE IF NOT EXISTS multipart_uploads (
|
|||||||
s3_key TEXT NOT NULL,
|
s3_key TEXT NOT NULL,
|
||||||
initiated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
|
initiated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
|
||||||
status VARCHAR DEFAULT 'in_progress',
|
status VARCHAR DEFAULT 'in_progress',
|
||||||
initiated_by TEXT
|
initiated_by TEXT,
|
||||||
|
content_type TEXT
|
||||||
);
|
);
|
||||||
|
|
||||||
CREATE TABLE IF NOT EXISTS multipart_parts (
|
CREATE TABLE IF NOT EXISTS multipart_parts (
|
||||||
|
|||||||
Reference in New Issue
Block a user