Releases: aurabx/harmony
Releases · aurabx/harmony
Harmony 0.12.3
chore: release 0.12.3
Harmony 0.12.2
chore: release 0.12.2
Harmony 0.12.1
chore: release 0.12.1
Harmony 0.12.0
Highlights
- Data mesh architecture with provider resolution and mesh authentication
- HTTPS/TLS support for secure connections
- Enhanced DICOM capabilities with C-STORE on SCU and improved protocol handling
- Version flag support for CLI
- Improved configuration management and cloud integration
- HTTP/3 (QUIC) support for both inbound listeners and outbound backends
- New middleware for DICOM to DICOMweb protocol translation
- Enhanced webhook middleware for event integration and audit logging
- Improved middleware type validation
Added
- (AURA-2241) Data mesh infrastructure
- Basic mesh data architecture and routing
- Mesh authentication and token management
- Route mesh ingress routes to matching endpoints
- Provider resolution for mesh participants
- Support for ingress/egress configuration in meshes
- (AURA-2240) HTTPS/TLS support for secure connections
- (AURA-2248) C-STORE support on DICOM SCU for sending datasets
- (AURA-2245) Provider resolution system
- CLI version flag (
--versionor-v) to display harmony version - Configuration push on startup option for cloud integration
- Support for
idfield on proxy and services configuration - Enhanced startup error messages for better diagnostics
- DICOM flatten support for left-side middleware
- C-STORE dataset available in envelope for middleware processing
- Basic DICOM keys added to DIMSE crate
- Build command for creating release binaries for testing
- HTTP/3 (QUIC) protocol support
- HTTP/3 inbound listeners with TLS configuration
- HTTP/3 backend connectivity for outbound requests
- Coexistence with HTTP/1.x and HTTP/2 on same network
- DICOM to DICOMweb middleware for protocol translation
- Enables DICOM SCP endpoints to proxy to DICOMweb-compatible backends
- Webhook middleware for event integration
- Integration with external event systems
Changed
- Migrated
backend_pathto services configuration - Token handling now saves tokens when provided via environment variables
- Management service organization improved
- Made JWT
_algfield optional for flexibility - Improved middleware type validation
Fixed
- Process no longer exits on invalid config reload (gracefully handles errors)
- Race conditions in DICOM port allocations resolved
- Base64 decoding issues on DICOMweb responses corrected
- DICOM to DICOMweb STOW functionality fixed
- PDU size support added for DICOM associations
- Various DICOM protocol-level fixes for improved stability
- Race conditions between cloud polling and force updates prevented
- Config writer bug fixed
- Safer handling for ingress/egress names in meshes
- Missing ingress/egress on mesh no longer causes fatal errors
- runbeam-sdk dependency issues resolved
- Test resource conflicts (dcmqrscp) resolved
- DICOMweb test stability improved
- Dev install script fixed
- Fixed validation failures for
jwt_authmiddleware - Missing targets no longer cause crashes during configuration validation
Documentation
- Provider and mesh documentation updates
Dependencies
- Internal crates updated to 0.12.0 (dimse, dicom_json_tool, harmony_transform, harmony-database, harmony-filesystem)
Harmony 0.10.1
This release fixes an issue where Target Details were constructed incorrectly in some kinds of pipelines.
Harmony 0.10.0
[0.10.0] - 2025-12-11
Added
- Debug logging support for JOLT transforms (enable with
debug = truein transform middleware config) - Environment variable validation:
proxy.required_env_varsfield enforces required environment variables at startup with clear error messages - Sensitive field patterns:
proxy.sensitive_field_patternsfield for log redaction rules - JWT authentication: Support for deprecated
leeway_secondsfield as fallback toleeway_secsfor backward compatibility
Changed
- Transform pipeline behavior improved for better handling of nested array structures
- Query parameter handling improved to preserve parameters set by middleware
- Target details now available earlier in the request processing pipeline
Fixed
- Transform arrays now handled correctly (via harmony-jolt 0.7)
- Query parameters are now properly cleared if provided by middleware
- Target details can now be set in transforms without requiring pre-existing entry
- Test suite improvements and stability fixes
Dependencies
- Updated harmony-jolt to 0.7.0 for improved array transformation handling
Harmony 0.9.0
Highlights
- Enhanced debugging and data transformation capabilities with new middleware
- Improved DICOM handling with structure flattening/unflattening
- Extended DIMSE SCP service with C-STORE support
- Configuration flexibility with environment variable replacement
- Refactored and streamlined DIMSE implementation
Added
- (AURA-2226) Data dumper middleware for inspecting and debugging pipeline data
- New
dicom_flattenanddicom_unflattenmiddleware for flattening DICOM structures in pipelines - Additional
left/righttransform application options in middleware configuration - Filesystem/S3 backend type
- Support C-STORE on the DIMSE SCP service
- Support for environment variable replacement in configuration files
Changed
- Transform pipeline now uses a more consistent internal data structure for normalized/transform data
- DIMSE crates (SCU/SCP) refactored to reduce reliance on dcmtk and improve maintainability
- Demo scripts updated to reflect current examples and configuration
- Minor internal cleanups
Fixed
- Transform behavior and FHIR DICOM example pipeline reliability improvements
- FHIR and FHIR-DICOM example authentication and configuration issues
- DIMSE task handling and related example correctness
- Doctest stability and test-only file handling
- Improved configuration error handling
- Config reload blocking on first run
Documentation
- General docs improvements and pass over existing content
- Chore-level documentation updates and AI assistant rules refinements
Harmony 0.8.0
Highlights
- Major authentication and authorization overhaul with new authentication handling system
- Normalized connection configuration support for all endpoint and backend types
- Updated to runbeam-sdk 0.9 for improved cloud integration
- Enhanced peer and target configuration with connection references
Breaking Changes
- Authentication system has been redesigned - old auth configurations need to be migrated to the new authentication handling system
- Backend and target configurations now support authorization settings that may require config updates
Added
- (AURA-2196) New authorization support for backends and targets
- Fine-grained authorization controls at the backend level
- Target-specific authorization configuration
- Integration with new authentication handling system
- (AURA-2196) Redesigned authentication handling system
- More flexible and extensible authentication framework
- Improved JWT token validation
- Better separation of authentication and authorization concerns
- (AURA-2205) Normalized ConnectionConfig support for all services
fhir,dicomweb,jmix, andechoendpoints now support connection settings- Backend services respect connection configuration including
base_pathand protocol-derived URLs - Configuration references via
target_refandpeer_reffor cleaner configuration
- (AURA-1973, AURA-2127) Basic peer and target configuration
- Foundation for peer-to-peer communication patterns
- Target configuration for more flexible routing
Changed
- Replaced existing authentication system with new authentication handling framework
- Enhanced configuration validation for connection settings
- Improved error messages for authentication and authorization failures
Fixed
- JWT token validation error that could cause authentication failures
- Connection configuration handling for various service types
Dependencies
- Updated runbeam-sdk to 0.9.0 (from 0.7.x)
- SDK update to 0.8 as intermediate step
Harmony 0.7.1
chore: release
Harmony 0.7.0
Changed
- Updated runbeam-sdk dependency to 0.7.x
- Improved config handling for cloud integration
- Standardized internal crate versions to 0.7.0 across workspace
- OpenSSL dependencies removed from build pipeline for improved cross-platform support
- Removed docker build dependencies (libdus) for production images
Fixed
- Runbeam authorization and config sync issues
- Default API URL configuration in cloud integration
- Test stability and reliability improvements
Dependencies
- Updated runbeam-sdk to 0.7.x
- Internal workspace crates (harmony-database, harmony-filesystem) bumped to 0.7.0