9.3.0

Platform Backend

This release updates the backend API contract for richer algorithm metadata and improves maintainability through dependency updates, focused DTO tests, and expanded repository documentation.

Added

• Optional documentation fields for algorithm and preprocessing specifications.
• Algorithm metadata fields for type, flags, validation datasets, cardinality constraints, and min/max bounds.
• validation_datasets support in algorithm execution request payloads.
• Structured handling for Exaflow status code 513.
• AlgorithmSpecificationDTOTest coverage for metadata deserialization, preprocessing order, optional documentation, dictionary metadata, and nested preprocessing serialization.
• Repository context documentation under docs/context.
• GitHub Copilot repository instructions.

Changed

• Updated algorithm/data-model DTOs to align with the newer Exaflow metadata contract.
• Refreshed pinned dependencies, including Spring Boot, PostgreSQL JDBC, Tomcat, Hibernate, Flyway, Gson, springdoc, Lombok, and Nimbus JOSE JWT.
• Expanded AGENTS.md with detailed contributor and agent guidance.

Fixed

• Preserved compatibility with older Exaflow responses where documentation fields are absent.
• Improved algorithm-result conversion for additional Exaflow error status handling.

9.2.1

Changelog:

• build: upgrade spring-boot-starter-parent to 4.0.6, tomcat to 11.0.22, and spring-security to 7.0.5

9.2.0

Changelog:

• feat: add custom exceptions for pathology access and availability and update DataModelService to handle empty results.

9.1.1

Release Notes

Fixes

• User: Fixed a silent failure that occurred when updating the agreeNDA status.

9.1.0

9.1.0 Platform Backend – Release Notes

Platform & Runtime

• Backend stack upgrade (Java 21 & Spring Boot 4):
  Upgraded the backend runtime and build stack to Java 21 and Spring Boot 4.
  This modernizes the platform foundation and ensures long-term support for the backend services.

• Dependency refresh:
  Updated core dependencies and libraries to newer major versions, including:

  • Flyway 12
  • Hibernate 7
  • PostgreSQL driver 42.7.10
  • Updated security and tooling libraries
    These updates improve compatibility, stability, and security across the backend.

---

Database

• Simplified Flyway migration structure:
  Consolidated database migrations into a single initial migration:

  V1__InitialSchema.sql

  This removes legacy baseline configuration logic and simplifies the database migration workflow for new deployments and environments.

• PostgreSQL image upgrade:
  Updated the deployment database image used by the platform backend to:

  postgres:18.3-alpine

---

Containerization

• Updated Docker runtime images:
  Migrated backend Docker build and runtime images to Amazon Corretto 21, aligning container images with the upgraded Java runtime.

• Dockerize upgrade:
  Updated the Dockerize utility used in the container startup process to a newer version for improved reliability during service initialization.

9.0.1

9.0.1 Platform Backend – Release Notes

Integration

• Gateway API → Exaflow integration:
  Replaced the previous Gateway API integration with direct integration to Exaflow.
  This aligns the backend with the exaflow layer and simplifies communication paths within the federated stack.

---

Authentication & Security

• Authentication fixes:
  Addressed issues in the authentication flow to improve reliability and correctness across API interactions.

• API key support:
  Added API key–based authentication mechanism to enable secure programmatic access and service-to-service communication.

---

Experiments & Metadata

• Platform version tracking for experiments:
  Introduced platform version metadata in experiment records.
  This allows:
  • Clear traceability of which platform version executed each experiment
  • Improved reproducibility
  • Easier debugging across releases

---

Internal Refactoring

• Exareme2 → Exaflow rename (internal variables):
  Updated internal variable names and references from exareme2 to exaflow to reflect the platform rebranding and maintain consistency across the codebase.