Skip to main content

2025.09.01 Release Notes

Assets

Docker Images

  • Registry Service: istaridigital.jfrog.io/customer-docker/registry-service:8.10.4
  • Frontend Service: istaridigital.jfrog.io/customer-docker/frontend-service:8.10.2
  • MCP Service: istaridigital.jfrog.io/customer-docker/mcp-service:0.1.36
  • Docs Service: istaridigital.jfrog.io/customer-docker/docs-service:6.5.0
  • SpiceDB: ghcr.io/authzed/spicedb:v1.39.1
  • SpiceDB Operator: ghcr.io/authzed/spicedb-operator:v1.18.0
  • Zitadel (main image): ghcr.io/zitadel/zitadel:v2.71.17
  • Zitadel (setup job): alpine/k8s:1.33.4

Helm Charts

  • SpiceDB Operator: helm pull --repo https://bushelpowered.github.io/spicedb-operator-chart spicedb-operator --version 2.0.0
  • Zitadel: helm pull --repo https://charts.zitadel.com zitadel --version 8.7.2
  • Istari-Platform Chart: helm pull oci://istaridigital.jfrog.io/customer-charts/istari-platform --version 3.0.0 --username ${ISTARI_ARTIFACTORY_USERNAME} --password ${ISTARI_ARTIFACTORY_PASSWORD}

SDK Clients

Agent

CLI

Integrations

Updates for the September 2025 Release

ModuleVersion
Dassault Systèmes 3DExperience CATIA (v6)1.3.0
Dassault Systèmes Cameo® Enterprise Architect3.0.0
Dassault Systèmes CATIA V52.4.0
Microsoft Office 3651.0.1
Microsoft Office Word2.3.1
Open PDF1.4.1
PTC Creo Parametric3.0.0

All Compatible Modules

Click to expand full module compatibility list for the September 2025 release of the Istari Platform
ModuleVersion
ANSYS HFSS1.0.1
Dassault Systèmes 3DExperience CATIA (v6)1.3.0
Dassault Systèmes Cameo® Enterprise Architect3.0.0
Dassault Systèmes CATIA V52.4.0
Google Slides0.2.0
MathWorks MATLAB (Base)2.1.0
MathWorks MATLAB Simulink1.1.0
Microsoft Office Excel2.3.0
Microsoft Office 3651.0.1
Microsoft Office PowerPoint1.1.0
Microsoft Office Word2.3.1
Hexagon MSC Nastran2.2.0
Hexagon Nastran Extract2.3.0
Open PDF1.4.1
Open Spreadsheets2.1.0
PTC Creo Parametric3.0.0

API Breaking Changes

istari-platform Helm Chart

The istari-platform Helm chart is now version 3.0.0 and comes with the following backwards-incompatible changes:

  1. The default value for mcp.secretName has now been set to istari-mcp instead of null to reflect that the Istari MCP service now requires that the Kubernetes secret istari-mcp must be present before deploying this new version of the Helm chart. This requires completing the following steps:
    1. Create a Zitadel application for the MCP service by following the Zitadel Configuration & Secrets - MCP Service Application step.
    2. Ensure that the previous default value for this key is not being overriden in your existing istari-values.yaml file
    3. Reference the Istari Platform install instructions on how to create this secret.
  2. The default registry for all images has been changed from "istaridigital.jfrog.io/main-docker-local" to "istaridigital.jfrog.io/customer-docker". This only impacts installations that do not use a private registry.
  3. We have a new OCI-compliant Helm repo that should be used when pulling the Helm chart. This is reflected in the install documentation and the above release assets.

Zitadel Upgrade/Changes

  • The bitnami/kubectl image is no longer publicly available. As a result, you will need to update the setupJob section of your zitadel-values.yaml file to use the following:

    zitadel-values.yaml
    setupJob:
    enabled: true
    machinekeyWriter:
    image:
    repository: "alpine/k8s"
    tag: "1.33.4"
  • Zitadel version update: In this release of Istari, the version of Zitadel has been updated to require Zitadel v2.71.17 to include several fixes and improvements. NOTE: in some environments, this update may disable any existing second factors established by users for authentication. A Zitadel administrator can remediate this by removing the second factor from those users, which will allow those users to log in and re-establish a second factor for authentication.

    • Updating from previously installed versions of Zitadel: In order to update from an older version of the Zitadel helm chart, you must first remove one of the existing resources managed by the existing helm chart. This resource can be deleted using the following command:

    kubectl delete deploy/zitadel

    • Ensure your helm charts refer to the correct Zitadel version: the correct version is specified in the Zitadel installation documentation, specifically the section illustrated below:
    zitadel-values.yaml
    image:
    repository: "ghcr.io/zitadel/zitadel"
    tag: "v2.71.17"
    • Updated guidance for SpiceDB network access: SpiceDB is required by the Istari platform for management of fine grained permissions. The documentation for SpiceDB configuration has been updated to remove guidance on creating a URL for SpiceDB that can be accessed outside of the cluster where Istari services reside. There should be no access granted to SpiceDB outside of Istari platform services.

Change Log

Istari Platform

New Features

  • Istari Remotes - Control Tag support: For installations with Istari Remotes configured for sharing with external Istari installations, control tags that are applied to models in the upstream owner's organization will be visible in the downstream organization, prefixed by the name of the sharing relationship configured in the downstream organization settings for remote sharing. The namespaced control tags are immediately granted to downstream remote relationship owners, and those tags can be granted to other users in the downstream organization by Istari Customer Administrators (as with other control tags).
  • Extract within System Users can now run extraction direction from a System in the WebUI
  • Bulk File Sharing from System Users can now bulk share files when sharing a System in the WebUI
  • Upload Files within System Users can now upload files directly from a System in the WebUI
  • System Event Logs Users can now view a history of changes (i.e., a new snapshot was created) for a System
  • Connected File Versioning
    You can now version connected files by reprocessing the same link. This enables seamless retriggers of extractions, workflows, and function executions simply by updating link parameters or re-running the process.
  • Multi-Tenancy in the Data Plane
    We now have full support for multi-tenant operations. Agents, jobs, and associated management UIs are strictly tenant-scoped, ensuring that workloads and resources cannot be shared across tenants. This provides stronger isolation and enterprise-ready scalability.

Agent

Updated configuration value names

The names of configuration values for the Istari Digital Agent in the istari_digital_config.yaml combined Istari Digital configuration have been updated for greater clarity and consistency with the rest of the Istari Platform.

The old names of the configuration values are deprecated but remain supported for backwards compatibility until further notice.

No immediate migration action is required, but Istari Digital recommends upgrading your istari_digital_config.yaml files to the new names as soon as possible.

Migration guide

To migrate, rename each configuration value for the Istari Digital Agent in istari_digital_config.yaml as follows:

Old nameNew name
istari_api_urlistari_digital_agent_registry_api_url
istari_agent_api_tokenistari_digital_agent_registry_api_token
istari_agent_display_nameistari_digital_agent_display_name
istari_agent_log_levelistari_digital_agent_log_level
module_configurationsistari_digital_agent_module_configurations
istari_agent_process_timeoutistari_digital_agent_process_timeout
istari_agent_poll_intervalistari_digital_agent_poll_interval
istari_agent_output_pathistari_digital_agent_output_path
istari_agent_headless_modeistari_digital_agent_headless_mode
istari_agent_status_update_retry_limitistari_digital_agent_status_update_retry_limit
istari_agent_download_retry_limitistari_digital_agent_download_retry_limit
istari_agent_upload_retry_limitistari_digital_agent_upload_retry_limit
istari_agent_upload_pool_sizeistari_digital_agent_upload_pool_size
istari_agent_private_key_pathistari_digital_agent_private_key_path
registry_urlistari_digital_agent_module_registry_url
registry_auth_tokenistari_digital_agent_module_registry_auth_token
registry_modules_repoistari_digital_agent_module_registry_repo
registry_modules_to_updateistari_digital_agent_module_registry_modules_to_update
istari_agent_sentry_dsnistari_digital_agent_sentry_dsn
istari_agent_sentry_enabledistari_digital_agent_sentry_enabled
istari_agent_sentry_environmentistari_digital_agent_sentry_environment

Handling of functions with optional model inputs

  • Support for functions with optional model inputs The Istari Digital Agent now properly processes inputs for functions with optional model inputs. This allows writing functions that take optional model inputs in addition to one or more required model model inputs.

Agents restricted to jobs created within their organization

Agents now have access exclusively to jobs created within their organization. This enhancement enforces organization-level restrictions, ensuring that agents can only operate on jobs generated by users in the same organization.

CLI

Schema Commands

stari schemas --help

  • Access and save JSON schemas for Istari Digital integration components: module manifest, function schema, function inputs, and function ouputs.

Function Test File Generation

stari function --help

  • Interactive test file generation: New stari function generate test_files command for creating input and output test files
  • Complex validation support: Full support for nested validation types like @object:[@string, @array:[@object:[@string, @number]]]
  • Placeholder mode: Generate files with realistic placeholder values for batch processing
  • Multi-function support: Generate test files for all functions in a manifest at once
  • Dynamic autocomplete: TAB completion for function names and implementation indices

Module Scaffolding System

stari module scaffold --help

  • Python module templates: Complete scaffolding for Python-based integrations
  • Development-ready setup: Generated projects include poetry, pre-commit hooks, testing framework, and build scripts
  • Smart templating: Automatic placeholder replacement in key files (pyproject.toml, module_manifest.json, README.md)

Module Script Execution

stari module run --help

  • Cross-platform script execution: Run module scripts defined in module_manifest.json with automatic OS detection
  • Dynamic autocomplete: TAB completion for available scripts and operating systems
  • Conflict detection: Prevents execution when the same OS appears in multiple script sections
  • Working directory management: Scripts run from the module root directory

Integrations

  • SharePoint Connected Files
    Introduced SharePoint integration, supporting connected file workflows for Office 365. You can now link and process files from Excel, Word, and PowerPoint stored in SharePoint, with seamless extraction and workflow support.
  • Office 365 Integration
    Broader integration with Office 365 services, enabling connected file handling across productivity workflows. You can now extract Office 365 excel files, via Sharepoint links.
  • OpenPDF Enhancements
    Updated OpenPDF integration with more efficient extractions, improved OCR (optical character recognition), and enhanced LLM-ready processing for complex documents.

Centralized Module Configuration Support

You can now configure supported modules — including PTC Creo Parametric, Dassault Systèmes Cameo® Enterprise Architect, Dassault Systèmes 3DExperience CATIA (v6), and Dassault Systèmes CATIA V5 — directly through a single, unified configuration file:
istari-digital-config.yml.

This enhancement streamlines module setup and management by consolidating all configuration details into one place. Teams can now:

  • Simplify onboarding and updates by managing all module definitions centrally.
  • Reduce configuration errors with consistent syntax and shared context across modules.
  • Align with Istari Agent and Istari CLI surfaces, ensuring the same configuration source is recognized across all Istari components.

Together, these improvements make module configuration more maintainable, transparent, and easier to automate.

Model Context Protocol (MCP) Service

New Features

  • Update Parameters
    • Users can now use the update parameter function for CATIA v5 and PTC CREO Models
  • OAuth
    • OAuth has been implemented to streamline integrating connecting LLMs with the MCP Service
    • Personal Access Token authentication is still enabled for programmatic connections via an MCP Client