Release: Alembic upgrade script for rule notification references wrong column
Motivation
----------
The upgrade script should be fixed in a hotfix release `1.19.0.post1` and the `1.19.0` release should be pulled from PyPi. This only impacts database upgrades from an older version.
diff --git a/lib/rucio/db/sqla/migrate_repo/versions/01eaf73ab656_add_new_rule_notification_state_progress.py b/lib/rucio/db/sqla/migrate_repo/versions/01eaf73ab656_add_new_rule_notification_state_progress.py
index 45c19452a..da93d7a01 100644
--- a/lib/rucio/db/sqla/migrate_repo/versions/01eaf73ab656_add_new_rule_notification_state_progress.py
+++ b/lib/rucio/db/sqla/migrate_repo/versions/01eaf73ab656_add_new_rule_notification_state_progress.py
@@ -36,7 +36,7 @@ def upgrade():
     if context.get_context().dialect.name not in ('sqlite'):  # pylint: disable=no-member
         drop_constraint('RULES_NOTIFICATION_CHK', 'rules', type_='check')
         create_check_constraint(name='RULES_NOTIFICATION_CHK', source='rules',
-                                condition="state in ('Y', 'N', 'C', 'P')")
+                                condition="notification in ('Y', 'N', 'C', 'P')")
 
 
 def downgrade():
@@ -46,4 +46,4 @@ def downgrade():
     if context.get_context().dialect.name not in ('sqlite'):  # pylint: disable=no-member
         drop_constraint('RULES_NOTIFICATION_CHK', 'rules', type_='check')
         create_check_constraint(name='RULES_NOTIFICATION_CHK', source='rules',
-                                condition="state in ('Y', 'N', 'C')")
+                                condition="notification in ('Y', 'N', 'C')")
['lib/rucio/db/sqla/migrate_repo/versions/01eaf73ab656_add_new_rule_notification_state_progress.py']