Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:

In this blog post, we will walk you through the highlights of these releases. For a complete overview, visit our release notes for the Java libraries, for the JavaScript libraries, and for the continuous delivery toolkit. The release notes also include the change log of all our releases so far.
At the end of the article, you will find a set of instructions on how to update to the new versions.

Java Libraries: Release Highlights 3.23.0

You can update your dependencies of the SAP Cloud SDK for Java to version 3.23.0 and get the new version from Maven Central.

This version contains several fixes and improvements.

The AuthTokenBuilder was improved so that public keys used for verification of authorization tokens created by it are now being cached.

Further improvements

Several further improvements are listed in the full release notes.

JavaScript Libraries: Release Highlights 1.22.0

The JavaScript libraries of the SAP Cloud SDK are now available in version 1.22.0.

Experimental OData v4 Support

Among some fixes for stability and correctnes, we introduced further OData v4 functionality. At this time, the OData v4 library is in an experimental state and might be subject to change. Stay tuned for the stable release in the upcoming weeks.

As usual, the full release notes contain a list of all improvements in this release.

Continuous Delivery Toolkit: Release Highlights v37

We have also released version v37 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.

Authenticated Access for Custom Defaults and Global Pipeline Extensions

We updated the download mechanism for custom defaults and global pipeline extensions so that both can also be stored on locations which are secured by basic authentication. You can find further details here.

Lint Stage

The pipeline can be configured to fail based on linting findings using the failOnError configuration option. By default, the pipeline does not fail based on lint findings.


We updated the bootstrapping Jenkinsfile so that it loads the pipeline directly from the library and not from the cloud-s4-sdk-pipeline git repository. This change improves efficiency of the pipeline because it decreases the number of repositories checked out and the number of executors during the pipeline run. The updated version of the Jenkinsfile can be found here.

Further improvements

You can find further fixes and improvements in the complete release notes.

How to Update

Java libraries

To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:

  • Open the pom.xml file in the root folder of your project.

  • Locate the dependency management section and therein the sdk-bom dependency.

  • Update the version of that dependency to 3.23.0.

With this, you are already done thanks to the "bill of material" (BOM) approach. Your dependency should look like this:
<!-- possibly further managed dependencies ... -->

If you update from a version prior to 3.0.0, have a look at our migration guide.

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 3.23.0.

Of course, you can also generate a new project that uses version 3.23.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=3.23.0 (or RELEASE).

JavaScript libraries

To update the version of the SAP Cloud SDK JavaScript libraries used in an existing project, use the command npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use npm outdated.

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:
./cx-server update image

Learn more about SAP Cloud SDK

To learn how others in the community use SAP Cloud SDK you can check out more related blog posts.

Are you interested in a particular topic? It might be helpful to search the Q&A place? Feel free to ask your question there and do not forget to select the tag SAP Cloud SDK.

If you are new to SAP Cloud SDK, get started and gain first hand-on exercise by following our tutorials.