Skip to content

πŸ™Œ OpenHands: AI-Driven Development

fix(migrations): add SETTING_UP_SKILLS to appconversationstarttaskstatus enum (#11780)

Tim O'Farrell9538c7bd8958
diff --git a/enterprise/migrations/versions/082_add_setting_up_skills_enum_value.py b/enterprise/migrations/versions/082_add_setting_up_skills_enum_value.py
new file mode 100644
index 0000000000..621767a2df
--- /dev/null
+++ b/enterprise/migrations/versions/082_add_setting_up_skills_enum_value.py
@@ -0,0 +1,39 @@
+"""Add SETTING_UP_SKILLS to appconversationstarttaskstatus enum
+
+Revision ID: 082
+Revises: 081
+Create Date: 2025-11-19 12:00:00.000000
+
+"""
+
+from typing import Sequence, Union
+
+from alembic import op
+
+# revision identifiers, used by Alembic.
+revision: str = '082'
+down_revision: Union[str, Sequence[str], None] = '081'
+branch_labels: Union[str, Sequence[str], None] = None
+depends_on: Union[str, Sequence[str], None] = None
+
+
+def upgrade() -> None:
+ """Add SETTING_UP_SKILLS enum value to appconversationstarttaskstatus."""
+ # Add the new enum value to the existing enum type
+ op.execute(
+ "ALTER TYPE appconversationstarttaskstatus ADD VALUE 'SETTING_UP_SKILLS'"
+ )
+
+
+def downgrade() -> None:
+ """Remove SETTING_UP_SKILLS enum value from appconversationstarttaskstatus.
+
+ Note: PostgreSQL doesn't support removing enum values directly.
+ This would require recreating the enum type and updating all references.
+ For safety, this downgrade is not implemented.
+ """
+ # PostgreSQL doesn't support removing enum values directly
+ # This would require a complex migration to recreate the enum
+ # For now, we'll leave this as a no-op since removing enum values
+ # is rarely needed and can be dangerous
+ pass