loud-france-86848
11/20/2023, 6:38 PMmetadata_service_container_image = "netflixoss/metaflow_metadata_service:v2.4.3"
ui_static_container_image = "public.ecr.aws/outerbounds/metaflow_ui:v1.1.2"average-beach-28850
11/20/2023, 7:26 PM1.3.6average-beach-28850
11/20/2023, 7:28 PMaverage-beach-28850
11/20/2023, 7:29 PMhundreds-midnight-75494
02/21/2024, 6:26 PMv1.3.10 I would expect being able to pull a container with that same image tag v1.3.10 but the gallery doesn't show one. Is it possible for you guys to add this automated build/tag feature to reflect your github releases?average-beach-28850
02/21/2024, 6:43 PM1.3.3 and v1.3.3 for backwards compatibility). The problem is that this is actually not fully automated and I kick off those builds in our CICD manually, so they're not 100% in synchundreds-midnight-75494
02/21/2024, 6:56 PMhundreds-midnight-75494
02/21/2024, 7:57 PMpublic.ecr.aws/outerbounds/metaflow_ui:v2.2.4 to be a newer version than v1.3.10 but I believe this version was one of the initial ones and must have been tagged in relation with the metaflow image version back then. Can you please delete that one so it doesn't confuse it?average-beach-28850
02/21/2024, 8:17 PMhundreds-midnight-75494
02/21/2024, 10:57 PMhundreds-midnight-75494
02/27/2024, 6:28 PMv2.2.4 from ECR, or at least retag to a version that doesn't clash with the new versioning scheme? TIA!average-beach-28850
02/27/2024, 6:52 PMhundreds-midnight-75494
02/27/2024, 6:53 PM