Release notes
Version 1.0.3 (October 29th, 2025)
This release includes various component bug and security fixes.
Features
- [Deployment Server] Automatically terminates long-unhealthy deployments for smoother operations.
- [Deployment Server] Allows reusing endpoint paths when a workspace is deleted or archived.
- [gRPC Gateway] Ensures MLOps API events are recorded in the audit trail with resource and request parameter details.
Fixes
- [Aggregator] Fixed bin edge and count calculation errors to ensure accurate metrics.
- [Deployment Server] Cleaned up stale log entries and correctly marked inactive deployments as terminated.
- [Deployment Server] Improved handling of numeric edge cases by filtering invalid values.
- [Storage] Restricted bootstrap to MLOps-related actions for stable initialization.
- [gRPC Gateway] Ensured MLOps API events are recorded in the audit trail with action values registered in Authz when available.
Python client v1.4.7
Fixes
- Disabled model registration during experiment linking to prevent unintended registrations.
Version 1.0.2 (October 10th, 2025)
This release includes various vulnerability fixes.
Fixes
- [Monitoring Migrator] Fixed an issue where migration failed when duplicate columns differed by letter case or data type.
- [Monitoring Frontend] Added support for alert and report notifications.
Version 1.0.1 (September 23rd, 2025)
Fixes
This release includes a vulnerability fix.
- [Monitoring Frontend] Applied vulnerability fixes.
Version 1.0.0 (July 31, 2025)
This release marks a significant milestone in the evolution of H2O MLOps. It introduces the following major changes:
- The legacy Wave-based UI and Admin Analytics app have been replaced by the unified H2O AI Cloud user interface.
- A fully featured and user-friendly Python client is now available, replacing the previously generated client.
- The Deployer component has been rewritten to address previous architectural limitations.
- A new monitoring solution has been added, based on aggregated data and Apache Superset.
See the full release notes below for a complete list of new features, and fixes.
New Features
- Introduced a new native user interface that replaces the legacy H2O Admin Analytics Wave app and the H2O MLOps Wave app.
- Added a new model monitoring solution based on aggregated data and Apache Superset. To learn more, see Model monitoring.
- Added support for using CSV files with headers as sink (input) for batch scoring jobs. For configuration details, see Batch scoring.
- Enabled support for using a public S3 bucket as the source for batch scoring jobs.
- Integrated H2O MLOps with H2O AI Cloud’s Authz service for authorization control.
- Integrated H2O MLOps with H2O AI Cloud’s Workspace service. All projects have been migrated to Workspaces.
- Integrated H2O MLOps with H2O AI Cloud’s User service.
- Added the ability to manually retry failed deployments.
- Added support for
AWS_MSK_IAMandSCRAMKafka authentication methods. - Added support for forwarding input scoring data to customer-specific Kafka topics.
- Integrated H2O MLOps with the Audit Trail component. All API interactions from H2O MLOps components are captured and sent to the Audit Trail service for processing. Users can view the collected data in the Audit Trail UI.
- Upgraded the MOJO library used in runtimes to version 2.8.9.1.
- Added support for H2O Driverless AI runtimes:
- 1.10.7.4
- 1.10.7.5
- 2.2.3
- 2.2.4
- Added support for specifying security contexts for all dynamically created pods, including batch scoring jobs, artifact fetchers, proxies, and runtimes.
- Added support for specifying affinity and tolerations in batch scoring jobs.
- Introduce competition statistics for batch scoring jobs.
- Introduce startup timeout option for batch scoring jobs and associated scorers.
Fixes
- Applied security fixes across all components.
- Allowed additional input fields beyond the expected schema in batch scoring jobs.
- Resolved Azure download timeout errors when Azure is used as the data source in batch scoring jobs.
- Added support for table names with special characters when using JDBC as the data source in batch scoring jobs.
- Fixed a segmentation fault that occurred during batch scoring when GCP was used as the data source.
- Corrected the supported MIME types for JDBC output sinks.
- Deployments are no longer processed sequentially.
- Prevented segmentation faults caused by concurrent hash generation in the security proxy component.
- Instead of failing whole batch scoring jobs when scoring fails, write the affected entry to error file and continue.
Python client v1.4.6
Fixes
- Added retry logic for workspace creation when personal workspaces cannot be resolved.
- Ensured additional fields are passed to MLOps APIs.
- Reverted unintended exposure of the deployment artifacts service.
Python client v1.4.5
Fixes
- Fixed an issue with preparing monitoring data for monitoring records.
Python client v1.4.4
Fixes
- Ensured that an isolated
httpxclient with a limited connection pool is used internally for native scorer support.
Python client v1.4.3
New features
- Exposed configurable API timeout settings.
Fixes
- Prevented retrieval of large experiment and dataset metadata by allowing retrieval based on user inputs only.