fix:null error

Author: anj20

…bb31b64_fix_wrong_stored_none_strings.py …rsions/6c44d67e505a_to_version_11_0_0.pymslib/mscolab/migrations/versions/d6777bb31b64_fix_wrong_stored_none_strings.py renamed to mslib/mscolab/migrations/versions/6c44d67e505a_to_version_11_0_0.py mslib/mscolab/migrations/versions/d6777bb31b64_fix_wrong_stored_none_strings.py renamed to mslib/mscolab/migrations/versions/6c44d67e505a_to_version_11_0_0.py

@@ -1,8 +1,8 @@
-"""Fix wrong stored None strings
+"""to_version_11_0_0
 
-Revision ID: d6777bb31b64
+Revision ID: 6c44d67e505a
 Revises: 922e4d9c94e2
-Create Date: 2025-02-04 22:46:11.605418
+Create Date: 2025-02-05 00:44:29.932413
 
 """
 from alembic import op
@@ -11,12 +11,13 @@
 
 
 # revision identifiers, used by Alembic.
-revision = 'd6777bb31b64'
+revision = '6c44d67e505a'
 down_revision = '922e4d9c94e2'
 branch_labels = None
 depends_on = None
 
 
+
 def upgrade():
     op.alter_column('changes', 'version_name', existing_type=sa.String(255), nullable=True)
     op.alter_column('changes', 'comment', existing_type=sa.String(255), nullable=True)