migration: widen routing tag

_sql/migrations/2024-05-14-024653_alter_inference_jobs_widen_routing_column/down.sql

@@ -0,0 +1,6 @@
+-- noinspection SqlDialectInspectionForFile
+-- noinspection SqlNoDataSourceInspectionForFile
+-- noinspection SqlResolveForFile
+
+ALTER TABLE generic_inference_jobs
+  CHANGE maybe_routing_tag maybe_routing_tag VARCHAR(32) DEFAULT NULL;

_sql/migrations/2024-05-14-024653_alter_inference_jobs_widen_routing_column/up.sql

@@ -0,0 +1,6 @@
+-- noinspection SqlDialectInspectionForFile
+-- noinspection SqlNoDataSourceInspectionForFile
+-- noinspection SqlResolveForFile
+
+ALTER TABLE generic_inference_jobs
+  CHANGE maybe_routing_tag maybe_routing_tag VARCHAR(64) DEFAULT NULL;

_sql/migrations_squashed/generic_inference_jobs.sql

@@ -166,7 +166,7 @@ CREATE TABLE generic_inference_jobs (
   -- The tag is typically added via a special HTTP header when the work
   -- is enqueued. In practice, this means we can canary deploy or cordon
   -- off special workers to handle certain jobs.
-  maybe_routing_tag VARCHAR(64) DEFAULT NULL, -- TODO(bt,2024-05-13): Widen column 32 --> 64 !!!
+  maybe_routing_tag VARCHAR(64) DEFAULT NULL,
 
   -- ========== JOB SYSTEM DETAILS ==========