Skip to content

Latest commit

 

History

History
211 lines (163 loc) · 4.88 KB

CHANGELOG.md

File metadata and controls

211 lines (163 loc) · 4.88 KB

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.5.1

Added

fixed

  • Update Spring Boot to version 3.2.5
  • Update Spring security to version 6.3.4

0.5.0

Added

fixed

  • Update spring framework to version 6.1.6
  • Update commons-io to version 2.17.0
  • Update lombock to version 1.18.34
  • Update velocity-engine-core to version 2.4
  • exlcude com.google.protobuf lib because of CVE https://avd.aquasec.com/nvd/2024/cve-2024-7254

0.4.0

Added

fixed

  • Implemented mandatory changes in licensing and legal documentation

0.3.2

Added

  • Update Springboot to version 3.2.4

fixed

  • security fix spring-web:6.1.5
  • security fix commons-compress:1.22

0.3.1

Added

  • Update Springboot to version 3.2.3

fixed

0.3.0

Added

Fixed

  • Generate diagrams with SVG Format

0.2.16

Added

Fixed

  • Spring Boot version updated to 3.1.6 to fix CVE-2023-34053
  • update Logback version to fix CVE-2023-6378
  • Enabled state transitions without modification of models.

0.2.15

Added

  • Added helm upgrade feature into helm test
  • Removed the docker apk upgrade and update commands.
  • Upgrade dependency to ESMF SDK 2.4.2

Fixed

  • Handled UrnSyntaxException.
  • Fixed the jena-fuseki-docker version to 4.7.0 for the test case.

0.2.14

Added

Fixed

  • Fixed CVE-2023-36478 | CWE-190 and CVE-2023-40167| CWE-130 Third-Party Components vulnerability.

0.2.13

Added

  • Added summary for the open api paths

Fixed

  • Fixed CVE-2023-36478 | CWE-190 and CVE-2023-40167| CWE-130 Third-Party Components vulnerability.

0.2.12

Added

Fixed

  • Fixed CVE-2022-44729| CWE-918 Third-Party Components vulnerability.

0.2.11-M1

Added

Fixed

  • Resource management adjusted for Kubernetes
  • Updated README.md file
  • Adding license header to missing files
  • Updated dependencies

0.2.10-M1

Added

Fixed

  • Fix CVE-2023-34035 (update springboot to version 3.1.2)
  • Fix CVE-2023-2976 (update google guava to version 32.1.1-jre)
  • Fix handle bamm and samm models.

0.2.9-M1

Added

Fixed

  • Added BAMM and SAMM Support

0.2.8-M1

Added

  • Update ESMF SDK to version 2.2.2

Fixed

0.2.7-M1

Added

  • Introduced a new Github action for build and publish the sldt-semantic-hub images to dockerhub.

Fixed

  • fix CVE-2023-20862
  • fix CVE-2023-20873

0.2.6-M1

Added

Fixed

  • Update DEPENDENCIES

0.2.5-M1

Added

Fixed

  • Fix cve-2023-20863 (update spring-core to 6.0.8)

0.2.4-M1

Added

Fixed

  • Adjust deployment to contain security context

0.2.3-M1

Added

Fixed

  • Fix cve-2023-20863 (update spring-expression to 6.0.8)

0.2.2-M1

Added

Fixed

  • Fix cve-2022-45688 (update json to 20230227)

Changed

0.2.1-M1

Added

Fixed

  • Update application to springboot 3.0.5 to fix vulnerability spring-expression

Changed

0.2.0-M1

Added

  • Add --no-cache to run apk in Dockerfile
  • Update application to springboot 3.0.1

Fixed

Changed

0.1.0-M3

Added

Fixed

  • Update jackson-databind to version 2.14.0
  • Update commons-text to version 1.10.0
  • Update snakeyaml to version 1.33

Changed

  • Update BAMM SDK from 2.0.0 to 2.0.6

0.1.0-M2

Added

  • Swagger UI now integrated with Portal Authentication
  • Filter endpoint for search of list of URNs
  • Helm Charts available via helm Repository at Eclipse Foundation

Fixed

  • Update jackson-databind to version 2.13.3
  • Update snakeyaml to version to 1.31

Changed

  • Update of Spring Boot version to 2.7.3

0.1.0-M1

Fixed

  • Adjust tests to avoid duplicates

Changed

  • Deactivate name search

0.0.1-M2

Added

  • The Semantic Hub now allows the generation and export of AAS files

Changed

  • Switched to BAMM SDK version 2.0.0

0.0.1-M1

Added

  • The Semantic Hub allows the creation, update, deletion of Semantic models in the RDF based format BAMM Aspect Meta Model (short BAMM)
  • Users can use the Semantic Hub API to view models and their meta information (such as version and current status, e.g. whether it is ready to be used)
  • The Semantic Hub provides endpoints to generate artifacts from the BAMM models:
    • example payload JSON
    • detailed HTML documentation describing the model
    • a diagram of the model
    • an OpenAPI description
    • an Asset Administration Shell representation of the model as a submodel template
    • a JSON schema representation of the model
  • The Semantic Hub allows the reuse of model components between different BAMM aspects and can resolve these dependencies
  • The Semantic Hub prevents unauthenticated access by checking whether an access token is provided by a CX user
  • The Semantic Hub enforces that only users with the correct role can read/create/update/delete semantic models