chore: bump for release v2.10.0

Author: topher

docker/README.md

@@ -32,7 +32,7 @@ FiftyOne Enterprise v2.9 no longer requires that operators set the
 following `FIFTYONE_DATABASE_ADMIN` variable while doing an initial installation:
 
 ```yaml
-# Required prior to 2.9.1
+# Required prior to 2.9
 services:
   fiftyone-app:
     environment:
@@ -433,7 +433,7 @@ might look like:
 ```yaml
 services:
   fiftyone-app:
-    image: voxel51/fiftyone-app-torch:v2.9.1
+    image: voxel51/fiftyone-app-torch:v2.10.0
 ```
 
 For more information, see the docs for

docker/common-services.yaml

@@ -1,7 +1,7 @@
 ---
 services:
   fiftyone-app-common:
-    image: voxel51/fiftyone-app:v2.9.1
+    image: voxel51/fiftyone-app:v2.10.0
     environment:
       API_URL: ${API_URL}
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
@@ -30,7 +30,7 @@ services:
     restart: always
 
   teams-api-common:
-    image: voxel51/fiftyone-teams-api:v2.9.1
+    image: voxel51/fiftyone-teams-api:v2.10.0
     environment:
       CAS_BASE_URL: ${CAS_BASE_URL:-http://teams-cas:3000/cas/api}
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
@@ -57,13 +57,13 @@ services:
     restart: always
 
   teams-app-common:
-    image: voxel51/fiftyone-teams-app:v2.9.1
+    image: voxel51/fiftyone-teams-app:v2.10.0
     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.9.1
+      FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION: 2.10.0
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
       FIFTYONE_SERVER_ADDRESS: ""
       FIFTYONE_SERVER_PATH_PREFIX: /api/proxy/fiftyone-teams
@@ -92,7 +92,7 @@ services:
     restart: always
 
   teams-cas-common:
-    image: voxel51/fiftyone-teams-cas:v2.9.1
+    image: voxel51/fiftyone-teams-cas:v2.10.0
     environment:
       CAS_DATABASE_NAME: ${CAS_DATABASE_NAME:-cas}
       CAS_DEFAULT_USER_ROLE: ${CAS_DEFAULT_USER_ROLE:-GUEST}
@@ -127,7 +127,7 @@ services:
         read_only: true
 
   teams-plugins-common:
-    image: voxel51/fiftyone-app:v2.9.1
+    image: voxel51/fiftyone-app:v2.10.0
     environment:
       API_URL: ${API_URL}
       FIFTYONE_AUTH_SECRET: ${FIFTYONE_AUTH_SECRET}
@@ -154,7 +154,7 @@ services:
     restart: always
 
   teams-do-common:
-    image: voxel51/fiftyone-teams-cv-full:v2.9.1
+    image: voxel51/fiftyone-teams-cv-full:v2.10.0
     deploy:
       replicas: ${FIFTYONE_DELEGATED_OPERATOR_WORKER_REPLICAS:-3}
     command: >

docker/docs/configuring-gpu-workloads.md

@@ -65,7 +65,7 @@ services:
       service: teams-do-common
 
   teams-do-with-gpu:
-    image: voxel51/fiftyone-teams-cv-full:v2.9.1
+    image: voxel51/fiftyone-teams-cv-full:v2.10.0
     deploy:
       replicas: ${FIFTYONE_DELEGATED_OPERATOR_WORKER_REPLICAS:-3}
     command: >

docker/docs/upgrading.md

@@ -78,9 +78,9 @@ quickstart  0.21.2
 
 ### From FiftyOne Enterprise Version 2.0.0 and Later
 
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
 1. Voxel51 recommends upgrading all FiftyOne Enterprise SDK users to FiftyOne Enterprise
-   version 2.9.1
+   version 2.10.0
     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`
@@ -121,7 +121,7 @@ To utilize the prior image, update your `common-services.yaml` similar to the be
 
 ```yaml
 teams-do-common:
-  image: voxel51/fiftyone-app:v2.9.1
+  image: voxel51/fiftyone-app:v2.10.0
 ```
 
 #### FiftyOne Enterprise v2.2+ Delegated Operator Changes
@@ -156,7 +156,7 @@ Additionally,
 
 ### From FiftyOne Enterprise Versions 1.6.0 to 1.7.1
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -191,15 +191,15 @@ Additionally,
    mv license.key "${LOCAL_LICENSE_FILE_DIR}/license"
    ```
 
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.9.1
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.10.0
     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.9.1
+    > **NOTE**: Any FiftyOne SDK less than 2.10.0
     > will lose connectivity at this point.
-    > Upgrading to `fiftyone==2.9.1` is required.
+    > Upgrading to `fiftyone==2.10.0` is required.
 
     ```shell
     FIFTYONE_DATABASE_ADMIN=true fiftyone migrate --all
@@ -213,7 +213,7 @@ Additionally,
 
 ### From FiftyOne Enterprise Version 1.1.0 and Before Version 1.6.0
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _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.
@@ -231,7 +231,7 @@ Additionally,
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -283,15 +283,15 @@ Additionally,
         unset FIFTYONE_DATABASE_ADMIN
         ```
 
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.9.1
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.10.0
     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.9.1
+    > **NOTE**: Any FiftyOne SDK less than 2.10.0
     > will lose connectivity at this point.
-    > Upgrading to `fiftyone==2.9.1` is required.
+    > Upgrading to `fiftyone==2.10.0` is required.
 
     ```shell
     FIFTYONE_DATABASE_ADMIN=true fiftyone migrate --all
@@ -322,14 +322,14 @@ Additionally,
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_ your users to
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _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.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -361,13 +361,13 @@ Additionally,
    `/cas/*` traffic to the `teams-cas` service.
    Example nginx configurations can be found
    [here](../)
-1. [Upgrade to FiftyOne Enterprise v2.9.1](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise v2.10.0](#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.9.1`
+    > Enterprise Database at this step until they upgrade to `fiftyone==2.10.0`
 
-1. Upgrade your FiftyOne SDKs to version 2.9.1
+1. Upgrade your FiftyOne SDKs to version 2.10.0
     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

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.9.1
+FIFTYONE_ENTERPRISE_VERSION=v2.10.0
 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.9.1
+    image: your-internal-registry/fiftyone-app-internal:v2.10.0
 ```
 
 Please see

helm/docs/upgrading.md

@@ -119,9 +119,9 @@ quickstart  0.21.2
 
 ### From FiftyOne Enterprise Version 2.0.0 or Higher
 
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
 1. Voxel51 recommends upgrading all FiftyOne Enterprise SDK users to FiftyOne Enterprise
-   version 2.9.1
+   version 2.10.0
     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`
@@ -143,7 +143,7 @@ quickstart  0.21.2
 
 <!-- Differs from docker-compose docs -->
 
-In `v2.9.1`, the `values.yaml` location of startup probe settings
+In `v2.10.0`, the `values.yaml` location of startup probe settings
 moved from `<settings>.service.startup` to `<settings>.startup` section.
 
 If your `values.yaml` contains
@@ -173,7 +173,7 @@ Repeat for each occurrence of `<settings>.service.startup` to `<settings>.startu
 
 FiftyOne Enterprise v2.7.0 deprecated the
 `delegatedOperatorExecutorSettings` setting in `values.yaml`.
-This has been removed in v2.9.1.
+This has been removed in v2.10.0.
 
 Please refer to
 [the delegated operator documentation](./configuring-delegated-operators.md#migrating-from-delegatedoperatorexecutorsettings-to-delegatedoperatordeployments)
@@ -308,7 +308,7 @@ For a full list of settings, please refer to the
 
 ### From FiftyOne Enterprise Versions 1.6.0 to 1.7.1
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -348,17 +348,17 @@ For a full list of settings, please refer to the
       fiftyone-license --from-file=license=./your-license-file
     ```
 
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.9.1
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.10.0
     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.9.1 will lose connectivity after
+    > **NOTE**: Any FiftyOne SDK less than 2.10.0 will lose connectivity after
     > this point.
-    > Upgrading all SDKs to `fiftyone==2.9.1` is recommended before migrating
+    > Upgrading all SDKs to `fiftyone==2.10.0` is recommended before migrating
     > your database.
 
     ```shell
@@ -373,7 +373,7 @@ For a full list of settings, please refer to the
 
 ### From FiftyOne Enterprise Versions After 1.1.0 and Before Version 1.6.0
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _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
@@ -392,7 +392,7 @@ For a full list of settings, please refer to the
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -432,17 +432,17 @@ For a full list of settings, please refer to the
     1. `secret.fiftyone.fiftyoneAuthSecret` (or your deployment's equivalent)
         1. This sets the `FIFTYONE_AUTH_SECRET` environment variable
            in the appropriate service pods
-1. [Upgrade to FiftyOne Enterprise version 2.9.1](#upgrading-from-previous-versions)
-1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.9.1
+1. [Upgrade to FiftyOne Enterprise version 2.10.0](#upgrading-from-previous-versions)
+1. Upgrade FiftyOne Enterprise SDK users to FiftyOne Enterprise version 2.10.0
     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.9.1 will lose connectivity after
+    > **NOTE**: Any FiftyOne SDK less than 2.10.0 will lose connectivity after
     > this point.
-    > Upgrading all SDKs to `fiftyone==2.9.1` is recommended before migrating
+    > Upgrading all SDKs to `fiftyone==2.10.0` is recommended before migrating
     > your database.
 
     ```shell
@@ -474,14 +474,14 @@ For a full list of settings, please refer to the
 
 ---
 
-> **NOTE**: Upgrading to FiftyOne Enterprise v2.9.1 _requires_
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _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.9.1 _requires_ a license file.
+> **NOTE**: Upgrading to FiftyOne Enterprise v2.10.0 _requires_ a license file.
 > Please contact your Customer Success Team before upgrading to FiftyOne Enterprise
 > 2.0 or beyond.
 >
@@ -520,10 +520,10 @@ For a full list of settings, please refer to the
       fiftyone-license --from-file=license=./your-license-file
     ```
 
-1. [Upgrade to FiftyOne Enterprise v2.9.1](#upgrading-from-previous-versions)
+1. [Upgrade to FiftyOne Enterprise v2.10.0](#upgrading-from-previous-versions)
     > **NOTE**: At this step, FiftyOne SDK users will lose access to the
-    > FiftyOne Enterprise Database until they upgrade to `fiftyone==2.9.1`
-1. Upgrade your FiftyOne SDKs to version 2.9.1
+    > FiftyOne Enterprise Database until they upgrade to `fiftyone==2.10.0`
+1. Upgrade your FiftyOne SDKs to version 2.10.0
     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

helm/fiftyone-teams-app/Chart.yaml

@@ -6,7 +6,7 @@ description: |
   FiftyOne Enterprise is the enterprise version of the open source [FiftyOne](https://github.com/voxel51/fiftyone) project.
   The FiftyOne Enterprise Helm chart is the recommended way to install and configure FiftyOne Enterprise on Kubernetes.
 type: application
-version: 2.9.1
-appVersion: "v2.9.1"
+version: 2.10.0
+appVersion: "v2.10.0"
 icon: https://voxel51.com/images/logo/voxel51-logo-horz-color-600dpi.png
 kubeVersion: ">=1.30-0"

helm/fiftyone-teams-app/README.md

@@ -15,7 +15,7 @@
 # fiftyone-teams-app
 
 <!-- markdownlint-disable line-length -->
-![Version: 2.9.1](https://img.shields.io/badge/Version-2.9.1-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v2.9.1](https://img.shields.io/badge/AppVersion-v2.9.1-informational?style=flat-square)
+![Version: 2.10.0](https://img.shields.io/badge/Version-2.10.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v2.10.0](https://img.shields.io/badge/AppVersion-v2.10.0-informational?style=flat-square)
 
 FiftyOne Enterprise is the enterprise version of the open source [FiftyOne](https://github.com/voxel51/fiftyone) project.
 The FiftyOne Enterprise Helm chart is the recommended way to install and configure FiftyOne Enterprise on Kubernetes.
@@ -49,7 +49,7 @@ FiftyOne Enterprise v2.9 no longer requires that operators set the
 following `FIFTYONE_DATABASE_ADMIN` variable while doing an initial installation:
 
 ```yaml
-# Required prior to 2.9.1
+# Required prior to 2.10.0
 appSettings:
   env:
     FIFTYONE_DATABASE_ADMIN: true
@@ -750,7 +750,7 @@ follow
 | teamsAppSettings.env.FIFTYONE_APP_ANONYMOUS_ANALYTICS_ENABLED | bool | `true` | Controls whether anonymous analytics are captured for the application. Set to false to opt-out of anonymous analytics. |
 | teamsAppSettings.env.FIFTYONE_APP_DEFAULT_QUERY_PERFORMANCE | bool | `true` | Controls whether Query Performance mode is enabled by default for every dataset for the teams application. Set to false to set default mode to off. |
 | teamsAppSettings.env.FIFTYONE_APP_ENABLE_QUERY_PERFORMANCE | bool | `true` | Controls whether Query Performance mode is enabled for the application. Set to false to disable Query Performance mode for entire application. |
-| teamsAppSettings.env.FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION | string | `"2.9.1"` | The recommended fiftyone SDK version that will be displayed in the install modal (i.e. `pip install ... fiftyone==0.11.0`). |
+| teamsAppSettings.env.FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION | string | `"2.10.0"` | The recommended fiftyone SDK version that will be displayed in the install modal (i.e. `pip install ... fiftyone==0.11.0`). |
 | teamsAppSettings.env.FIFTYONE_APP_THEME | string | `"dark"` | The default theme configuration. `dark`: Theme will be dark when user visits for the first time. `light`: Theme will be light theme when user visits for the first time. `always-dark`: Sets dark theme on each refresh (overrides user theme changes in the app). `always-light`: Sets light theme on each refresh (overrides user theme changes in the app). |
 | teamsAppSettings.env.RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED | bool | `false` | Disable duplicate atom/selector key checking that generated false-positive errors. [Reference][recoil-env]. |
 | teamsAppSettings.fiftyoneApiOverride | string | `""` | Overrides the `FIFTYONE_API_URI` environment variable. When set `FIFTYONE_API_URI` controls the value shown in the API Key Modal providing guidance for connecting to the FiftyOne Enterprise API. `FIFTYONE_API_URI` uses the value from apiSettings.dnsName if it is set, or uses the teamsAppSettings.dnsName |