chore(versions): Bump for 2.19.1

Makefile

@@ -1,6 +1,6 @@
 SHELL := $(SHELL) -e
 ASDF := $(shell asdf where golang)
-VERSION ?= 2.19.0
+VERSION ?= 2.19.1
 
 # Help
 .PHONY: $(shell sed -n -e '/^$$/ { n ; /^[^ .\#][^ ]*:/ { s/:.*$$// ; p ; } ; }' $(MAKEFILE_LIST))

docker/README.md

@@ -240,7 +240,7 @@ You can override the default image used by any service in
 ```yaml
 services:
   fiftyone-app:
-    image: voxel51/fiftyone-app-torch:v2.19.0
+    image: voxel51/fiftyone-app-torch:v2.19.1
 ```
 
 > [!NOTE]

docker/common-services.yaml

@@ -1,7 +1,7 @@
 ---
 services:
   fiftyone-app-common:
-    image: voxel51/fiftyone-app:v2.19.0
+    image: voxel51/fiftyone-app:v2.19.1
     environment:
       API_URL: ${API_URL}
       FIFTYONE_APP_DEFAULT_QUERY_PERFORMANCE: ${FIFTYONE_APP_DEFAULT_QUERY_PERFORMANCE}
@@ -33,7 +33,7 @@ services:
     restart: always
 
   teams-api-common:
-    image: voxel51/fiftyone-teams-api:v2.19.0
+    image: voxel51/fiftyone-teams-api:v2.19.1
     environment:
       API_EXTERNAL_URL: ${FIFTYONE_API_URI}
       CAS_BASE_URL: ${CAS_BASE_URL:-http://teams-cas:3000/cas/api}
@@ -63,13 +63,13 @@ services:
     restart: always
 
   teams-app-common:
-    image: voxel51/fiftyone-teams-app:v2.19.0
+    image: voxel51/fiftyone-teams-app:v2.19.1
     environment:
       API_URL: ${API_URL}
       APP_USE_HTTPS: ${APP_USE_HTTPS:-true}
       FIFTYONE_API_URI: ${FIFTYONE_API_URI:-"Please contact your Admin for an API URI"}
       FIFTYONE_APP_ALLOW_MEDIA_EXPORT: ${FIFTYONE_APP_ALLOW_MEDIA_EXPORT:-true}
-      FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION: 2.19.0
+      FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION: 2.19.1
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
       FIFTYONE_SERVER_ADDRESS: ""
       FIFTYONE_SERVER_PATH_PREFIX: /api/proxy/fiftyone-teams
@@ -98,7 +98,7 @@ services:
     restart: always
 
   teams-cas-common:
-    image: voxel51/fiftyone-teams-cas:v2.19.0
+    image: voxel51/fiftyone-teams-cas:v2.19.1
     environment:
       CAS_DATABASE_NAME: ${CAS_DATABASE_NAME:-cas}
       CAS_DEFAULT_USER_ROLE: ${CAS_DEFAULT_USER_ROLE:-GUEST}
@@ -133,7 +133,7 @@ services:
         read_only: true
 
   teams-plugins-common:
-    image: voxel51/fiftyone-app-torch:v2.19.0
+    image: voxel51/fiftyone-app-torch:v2.19.1
     environment:
       API_URL: ${API_URL}
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
@@ -161,7 +161,7 @@ services:
     restart: always
 
   teams-do-common:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     # Telemetry default-on requires teams-do to share its PID namespace
     # with a single sidecar (compose's `pid: "service:<name>"` only joins
     # one replica). Force replicas=1 to keep the 1:1 pairing deterministic.
@@ -215,7 +215,7 @@ services:
   # target's PID namespace so the sidecar can read /proc/<pid>/fd/1 and
   # psutil can see the target's process.
   fiftyone-app-telemetry-common:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:fiftyone-app"
     # Matches the workload image's USER 1000:1000 so the kernel's
     # ptrace_may_access() check on /proc/<workload-pid>/fd/1 reads passes via the
@@ -242,7 +242,7 @@ services:
     restart: always
 
   teams-api-telemetry-common:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:teams-api"
     user: "1000:1000"
     cap_drop:
@@ -266,7 +266,7 @@ services:
     restart: always
 
   teams-plugins-telemetry-common:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:teams-plugins"
     user: "1000:1000"
     cap_drop:
@@ -290,7 +290,7 @@ services:
     restart: always
 
   teams-do-telemetry-common:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:teams-do"
     user: "1000:1000"
     cap_drop:

docker/docs/configuring-gpu-workloads.md

@@ -73,7 +73,7 @@ services:
       service: teams-do-common
 
   teams-do-with-gpu:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     command: >
       /bin/sh -c "fiftyone delegated launch -t remote  -n 'teams-do-with-gpu' -m"
     environment:

docker/docs/upgrading.md

@@ -84,9 +84,9 @@ quickstart  0.21.2
 
 ### From FiftyOne Enterprise Version 2.0.0 and Later
 
-1. [Upgrade to FiftyOne Enterprise version 2.19.0](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise version 2.19.1](#upgrading-from-previous-versions)
 1. Voxel51 recommends upgrading all FiftyOne Enterprise SDK users to FiftyOne Enterprise
-   version 2.19.0
+   version 2.19.1
     1. Login to the FiftyOne Enterprise UI
     1. To obtain the CLI command to install the FiftyOne SDK associated with
       your FiftyOne Enterprise version, navigate to `Account > Install FiftyOne`
@@ -281,7 +281,7 @@ To utilize the prior image, update your `common-services.yaml` similar to the be
 
 ```yaml
 teams-do-common:
-  image: voxel51/fiftyone-app:v2.19.0
+  image: voxel51/fiftyone-app:v2.19.1
 ```
 
 #### FiftyOne Enterprise v2.2+ Delegated Operator Changes
@@ -316,7 +316,7 @@ Additionally,
 
 ### From FiftyOne Enterprise Versions 1.6.0 to 1.7.1
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.0 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.1 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -351,15 +351,15 @@ Additionally,
    mv license.key "${LOCAL_LICENSE_FILE_DIR}/license"
    ```
 
-1. [Upgrade to FiftyOne Enterprise version 2.19.0](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.19.0
+1. [Upgrade to FiftyOne Enterprise version 2.19.1](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.19.1
     1. Login to the FiftyOne Enterprise UI
     1. To obtain the CLI command to install the FiftyOne SDK associated with
       your FiftyOne Enterprise version, navigate to `Account > Install FiftyOne`
 1. Upgrade all the datasets
-    > **NOTE**: Any FiftyOne SDK less than 2.19.0
+    > **NOTE**: Any FiftyOne SDK less than 2.19.1
     > will lose connectivity at this point.
-    > Upgrading to `fiftyone==2.19.0` is required.
+    > Upgrading to `fiftyone==2.19.1` is required.
 
     ```shell
     FIFTYONE_DATABASE_ADMIN=true fiftyone migrate --all
@@ -373,7 +373,7 @@ Additionally,
 
 ### From FiftyOne Enterprise Version 1.1.0 and Before Version 1.6.0
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.0 _requires_
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.1 _requires_
 > your users to log in after the upgrade is complete.
 > This will interrupt active workflows in the FiftyOne Enterprise Hosted Web App.
 > You should coordinate this upgrade carefully with your end-users.
@@ -391,7 +391,7 @@ Additionally,
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.0 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.1 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -443,15 +443,15 @@ Additionally,
         unset FIFTYONE_DATABASE_ADMIN
         ```
 
-1. [Upgrade to FiftyOne Enterprise version 2.19.0](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.19.0
+1. [Upgrade to FiftyOne Enterprise version 2.19.1](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.19.1
     1. Login to the FiftyOne Enterprise UI
     1. To obtain the CLI command to install the FiftyOne SDK associated with
       your FiftyOne Enterprise version, navigate to `Account > Install FiftyOne`
 1. Upgrade all the datasets
-    > **NOTE**: Any FiftyOne SDK less than 2.19.0
+    > **NOTE**: Any FiftyOne SDK less than 2.19.1
     > will lose connectivity at this point.
-    > Upgrading to `fiftyone==2.19.0` is required.
+    > Upgrading to `fiftyone==2.19.1` is required.
 
     ```shell
     FIFTYONE_DATABASE_ADMIN=true fiftyone migrate --all
@@ -482,14 +482,14 @@ Additionally,
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.0 _requires_ your users to
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.1 _requires_ your users to
 > log in after the upgrade is complete.
 > This will interrupt active workflows in the FiftyOne Enterprise Hosted Web App.
 > You should coordinate this upgrade carefully with your end-users.
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.0 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.19.1 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -520,13 +520,13 @@ Additionally,
 1. Update your web server routes to include routing
    `/cas/*` traffic to the `teams-cas` service.
    Please see our [example nginx configurations](../) for more information.
-1. [Upgrade to FiftyOne Enterprise v2.19.0](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise v2.19.1](#upgrading-from-previous-versions)
    with `FIFTYONE_DATABASE_ADMIN=true`
    (this is not the default for this release).
     > **NOTE**: FiftyOne SDK users will lose access to the FiftyOne
-    > Enterprise Database at this step until they upgrade to `fiftyone==2.19.0`
+    > Enterprise Database at this step until they upgrade to `fiftyone==2.19.1`
 
-1. Upgrade your FiftyOne SDKs to version 2.19.0
+1. Upgrade your FiftyOne SDKs to version 2.19.1
     1. Login to the FiftyOne Enterprise UI
     1. To obtain the CLI command to install the FiftyOne SDK associated
       with your FiftyOne Enterprise version, navigate to

docker/internal-auth/compose.delegated-operators.gpu.yaml

@@ -19,7 +19,7 @@
 #  https://github.com/voxel51/fiftyone-teams-app-deploy/tree/main/docker#environment-proxies
 services:
   teams-do-gpu:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["gpu"]
     shm_size: "8g"
     command: >
@@ -51,7 +51,7 @@ services:
     restart: always
 
   teams-do-gpu-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:teams-do-gpu"
     profiles: ["gpu"]
     user: "1000:1000"

docker/internal-auth/compose.delegated-operators.yaml

@@ -28,7 +28,7 @@ services:
   # distinct orchestrator name so it surfaces separately in the
   # Settings → Metrics UI.
   teams-do-2:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["do-2", "do-3"]
     deploy:
       replicas: 1
@@ -51,7 +51,7 @@ services:
       - telemetry-socket-2:/tmp/telemetry
 
   teams-do-2-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     profiles: ["do-2", "do-3"]
     pid: "service:teams-do-2"
     user: "1000:1000"
@@ -92,7 +92,7 @@ services:
   # Slot 3 — included by the `do-3` profile. Mirror of slot 2 with its
   # own socket volume and orchestrator name.
   teams-do-3:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["do-3"]
     deploy:
       replicas: 1
@@ -115,7 +115,7 @@ services:
       - telemetry-socket-3:/tmp/telemetry
 
   teams-do-3-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     profiles: ["do-3"]
     pid: "service:teams-do-3"
     user: "1000:1000"

docker/legacy-auth/compose.delegated-operators.gpu.yaml

@@ -19,7 +19,7 @@
 #  https://github.com/voxel51/fiftyone-teams-app-deploy/tree/main/docker#environment-proxies
 services:
   teams-do-gpu:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["gpu"]
     shm_size: "8g"
     command: >
@@ -51,7 +51,7 @@ services:
     restart: always
 
   teams-do-gpu-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     pid: "service:teams-do-gpu"
     profiles: ["gpu"]
     user: "1000:1000"

docker/legacy-auth/compose.delegated-operators.yaml

@@ -28,7 +28,7 @@ services:
   # distinct orchestrator name so it surfaces separately in the
   # Settings → Metrics UI.
   teams-do-2:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["do-2", "do-3"]
     deploy:
       replicas: 1
@@ -51,7 +51,7 @@ services:
       - telemetry-socket-2:/tmp/telemetry
 
   teams-do-2-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     profiles: ["do-2", "do-3"]
     pid: "service:teams-do-2"
     user: "1000:1000"
@@ -94,7 +94,7 @@ services:
   # for higher worker counts use the helm chart, which adds a sidecar
   # to every pod automatically.
   teams-do-3:
-    image: voxel51/fiftyone-teams-cv-full:v2.19.0
+    image: voxel51/fiftyone-teams-cv-full:v2.19.1
     profiles: ["do-3"]
     deploy:
       replicas: 1
@@ -117,7 +117,7 @@ services:
       - telemetry-socket-3:/tmp/telemetry
 
   teams-do-3-telemetry:
-    image: voxel51/telemetry-sidecar:v2.19.0
+    image: voxel51/telemetry-sidecar:v2.19.1
     profiles: ["do-3"]
     pid: "service:teams-do-3"
     user: "1000:1000"

docs/custom-plugins.md

@@ -46,7 +46,7 @@ With a Dockerfile like this, you could use the following commands to
 build, and publish, your image to your internal registry
 
 ```shell
-FIFTYONE_ENTERPRISE_VERSION=v2.19.0
+FIFTYONE_ENTERPRISE_VERSION=v2.19.1
 docker buildx build --push \
   --build-arg FIFTYONE_ENTERPRISE_IMAGE_NAME="voxel51/fiftyone-app:${FIFTYONE_ENTERPRISE_VERSION}" \
   -t your-internal-registry/fiftyone-app-internal:${FIFTYONE_ENTERPRISE_VERSION} .
@@ -63,7 +63,7 @@ After your custom plugins image is built, you can add it to your
 ```yaml
 services:
   teams-plugins:
-    image: your-internal-registry/fiftyone-app-internal:v2.19.0
+    image: your-internal-registry/fiftyone-app-internal:v2.19.1
 ```
 
 Please see

docs/orchestrators/configuring-databricks-orchestrator.md

@@ -87,7 +87,7 @@ w = WorkspaceClient()
 DBFS_PATH = "/FileStore/my_project/requirements.txt"
 
 PYTHON_DEPENDENCIES = [
-   "fiftyone==2.19.0",  # use your FiftyOne version here
+   "fiftyone==2.19.1",  # use your FiftyOne version here
    "ultralytics",
    "torch",
    "transformers",

docs/orchestrators/configuring-kubernetes-orchestrator.md

@@ -488,7 +488,7 @@ spec:
   shareProcessNamespace: true
   initContainers:
     - name: telemetry-sidecar
-      image: voxel51/telemetry-sidecar:v2.19.0
+      image: voxel51/telemetry-sidecar:v2.19.1
       restartPolicy: Always
       securityContext:
         # The sidecar image runs as root (SYS_PTRACE +
@@ -649,7 +649,7 @@ spec:
       shareProcessNamespace: true
       initContainers:
       - name: telemetry-sidecar
-        image: voxel51/telemetry-sidecar:v2.19.0
+        image: voxel51/telemetry-sidecar:v2.19.1
         restartPolicy: Always
         securityContext:
           # The sidecar image runs as root (SYS_PTRACE +