Version 1.4.1 fixes an issue where destinations with protocol HTTP (instead of HTTPS) led to an error like Protocol "http:" not supported. Expected "https:".
We have also fixed an issue where the deserialization of certain entities would fail due to cyclic dependencies across linked entities. This cyclic dependency caused entities to be undefined and led to error messages such as Cannot read property 'builder' of undefined.
Version v20 runs the stages for frontend unit tests, Checkmarx, and Fortify on Java, Node.js and HTML5 modules of multi-target applications.
If the Checkmarx plugin reports a build failure, the pipeline now aborts the build so that the pipeline run is not marked as success when Checkmarx may actually hav severe findings. This is a potentially breaking change for projects above the threshold.
If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace sdk-bom with sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 2.18.0.
Of course, you can also generate a new project that uses version 2.18.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=2.18.0 (or RELEASE).
Continuous Delivery Toolkit
If you are using the pipeline with a fixed version (as recommended since v7), update the continuous delivery toolkit with the following command, that you run on the server hosting the cx-server: