SAP · marikaner · Jan 5, 2026 · Jan 2, 2026 · Jan 5, 2026
diff --git a/docs-java/environments/gardener.mdx b/docs-java/environments/gardener.mdx
@@ -356,7 +356,6 @@ spec:
    This secret will contain the actual service binding information.
 
 4. Mount the `my-destination-service-secret` secret into the file system of the application as follows:
-
    1. Find the empty list of `volumes` at the end of your `deployment.yml`.
       Add a new volume, referencing the secret:
 

diff --git a/docs-java/environments/kyma.mdx b/docs-java/environments/kyma.mdx
@@ -329,7 +329,6 @@ For this guide we'll assume we want to use two services:
 
 5. The automatically created secret (derived from the service binding) needs to be mounted to the file system of your application pods.
    Open your `deployment.yml` and add the following content:
-
    1. Find the empty list of `volumes` in your `deployment.yml`.
       Add a new volume, referencing the secret:
 

diff --git a/docs-java/features/connectivity/006-running-locally.mdx b/docs-java/features/connectivity/006-running-locally.mdx
@@ -148,7 +148,6 @@ cf restart app-name
 ```
 
 - Inspect the value of the entry `connectivity` of your `VCAP_SERVICES` and take note of the values of the fields
-
   - `credentials.onpremise_proxy_port` (we will refer to the value as _proxy-port_ hereafter)
   - `credentials.onpremise_proxy_host` (we will refer to the value as _proxy-host_ hereafter)
 

diff --git a/docs-java/release-notes/release-notes-0-to-14.mdx b/docs-java/release-notes/release-notes-0-to-14.mdx
@@ -287,7 +287,6 @@
 - The de-facto standard `resilience4j` implementation for the resilience API is now included by default.
   In case you are loading a different implementation of the `Resilience4jDecorationStrategy` via the Java Service Provider Interface (SPI), you should use `resilience-api` and ensure `resilience4j` is not loaded transitively.
   Alternatively, you can invoke `ResilienceDecorator.setDecorationStrategy` explicitly in your code.
-
   - In case you are using custom facade implementations for accessors (e.g. `TenantAccessor`) this might have additional implications.
 
         <details>

diff --git a/...cs/version-v3/environments/sap-btp-kubernetes-environment-with-sap-gardener.mdx b/...cs/version-v3/environments/sap-btp-kubernetes-environment-with-sap-gardener.mdx
@@ -357,7 +357,6 @@ spec:
    This secret will contain the actual service binding information.
 
 4. Mount the `my-destination-service-secret` secret into the file system of the application as follows:
-
    1. Find the empty list of `volumes` at the end of your `deployment.yml`.
       Add a new volume, referencing the secret:
 
@@ -596,7 +595,6 @@ The following guide will show you what has to be done to create and use it.
    :::
 
 4. Now we need to download the CA certificate of the connectivity service and create a secret containing:
-
    - The CA certificate of the connectivity service
    - Our private key
    - Our public certificate

diff --git a/docs-java_versioned_docs/version-v3/environments/sap-btp-kyma-environment.mdx b/docs-java_versioned_docs/version-v3/environments/sap-btp-kyma-environment.mdx
@@ -418,7 +418,6 @@ spec:
    This secret will contain the actual service binding information.
 
 4. Mount the `my-dest-secret` secret into the file system of the application as follows:
-
    1. Find the empty list of `volumes` at the end of your `deployment.yml`.
       Add a new volume, referencing the secret:
 

diff --git a/docs-java_versioned_docs/version-v3/release-notes/release-notes-0-to-14.mdx b/docs-java_versioned_docs/version-v3/release-notes/release-notes-0-to-14.mdx
@@ -88,7 +88,6 @@
 ### New Functionality
 
 - Introduce a new [`BasicAuthenticationAccessor`](https://help.sap.com/doc/4cc23f4c3bf147fe834fbd0e3413e5d5/1.0/en-US/index.html?com/sap/cloud/sdk/cloudplatform/security/BasicAuthenticationAccessor.html) to read the username and password from the Basic Authentication header of the currently incoming request on Cloud Foundry.
-
   - Use it like the other `*Accessor` classes:
 
     ```
@@ -112,7 +111,6 @@
   A valid JWT takes precedence over a Basic Authentication header.
 
   The order of resolution is
-
   1. If a principal is given in the current context (e.g. via [`PrincipalAccessor.executeWithPrincipal()`](https://help.sap.com/doc/4cc23f4c3bf147fe834fbd0e3413e5d5/1.0/en-US/com/sap/cloud/sdk/cloudplatform/security/principal/PrincipalAccessor.html#executeWithPrincipal-com.sap.cloud.sdk.cloudplatform.security.principal.Principal-java.util.concurrent.Callable-)), this will we be used.
   2. Otherwise, if a JWT is given in the current context (e.g. via an incoming request or manually set via the [`AuthTokenAccessor.executeWithAuthToken()`](https://help.sap.com/doc/4cc23f4c3bf147fe834fbd0e3413e5d5/1.0/en-US/com/sap/cloud/sdk/cloudplatform/security/AuthTokenAccessor.html#executeWithAuthToken-com.sap.cloud.sdk.cloudplatform.security.AuthToken-java.util.concurrent.Callable-) methods) the principal is read from there.
   3. Otherwise, If there is no JWT or the resolution fails the user retrieved via the [`BasicAuthenticationAccessor`](https://help.sap.com/doc/4cc23f4c3bf147fe834fbd0e3413e5d5/1.0/en-US/index.html?com/sap/cloud/sdk/cloudplatform/security/BasicAuthenticationAccessor.html) used (if existent).
@@ -123,7 +121,6 @@
 ### Improvements
 
 - The connectivity to On-Premise systems from SCP Cloud Foundry is updated, so that the [authentication](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/39f538ad62e144c58c056ebc34bb6890.html) now follows the [recommended](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/39f538ad62e144c58c056ebc34bb6890.html) protocol for principal propagation.
-
   - Instead of populating two headers `SAP-Connectivity-Authentication` and `Proxy-Authorization` for On-Premise requests, the SAP Cloud SDK now takes the recommended approach of just using `Proxy-Authorization` with a dynamically resolved _User Exchange Access Token_.
   - Introduce `PrincipalPropagationStrategy` for configuring that the previous behavior should be used.
 
@@ -401,7 +398,6 @@
 - _OData VDM Generator_: add deprecation information contained in the provided Swagger file of a service to generated service classes.
 
 - Update dependencies:
-
   - Java libraries of [SAP Cloud Application Programming Model](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/00823f91779d4d42aa29a498e0535cdf.html) (`com.sap.cloud.servicesdk.*`) from version 1.32.0 to 1.32.5
   - Caffeine from 2.7.0 to 2.8.0
   - Commons Codec from 1.12.0 to 1.13.0
@@ -469,7 +465,6 @@ Either update to version `3.1.0` or manually add the following properties to the
   - Removed the PLATFORM_DEFAULT value from all destination retrieval strategy enums.
     - Use null values instead, or do not set the parameter at all.
 - Removed the destination retrieval strategy configuration from the DestinationAccessor. It is no longer a global configuration by destination name.
-
   - Destination retrieval strategy configuration is now stored in instances of the new DestinationOptions class.
   - To set the destination retrieval strategy, use the ScpCfDestinationOptionsHelper or ScpNeoDestinationOptionsHelper with the builder of DestinationOptions.
   - e.g. on Cloud Foundry:

diff --git a/docs-java_versioned_docs/version-v3/release-notes/release-notes-15-to-29.mdx b/docs-java_versioned_docs/version-v3/release-notes/release-notes-15-to-29.mdx
@@ -19,7 +19,6 @@
 - The improved OData v2 type-safe client is now Generally Available.
   From now on we recommend it for OData API consumption.
   Refer to the [documentation on how to switch](https://sap.github.io/cloud-sdk/docs/java/v3/features/odata/type-safe-client-odata-v2.mdx#switch-to-improved-odata-v2-type-safe-client) for more details on the new OData 2 client.
-
   - The methods `executeRequest` are no longer marked as Beta and ready for use in production code.
   - The new methods `matchAnyVersionIdentifier()` and `disableVersionIdentifier()` allow for better control over [ETag handling](https://sap.github.io/cloud-sdk/docs/java/v3/features/odata/type-safe-client-odata-v2.mdx#handling-of-etags).
 
@@ -243,7 +242,6 @@ final DefaultHttpDestination defaultHttpDestination =
   - Update [SAP Cloud Application Programming Model](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/00823f91779d4d42aa29a498e0535cdf.html) from version `1.40.2` to `1.40.6`
   - Update [SAP Cloud Security Client](https://github.com/SAP/cloud-security-xsuaa-integration) from `2.7.3` to `2.7.5`
 - Update Maven plugins in Maven archetypes:
-
   - Archetype `scp-cf-tomee`:
     - Update `tomee-maven-plugin` from `8.0.1` to `8.0.3`
   - Archetype `scp-cf-tomee` and `neo-javaee7`:
@@ -286,7 +284,6 @@ Release date: July 16, 2020
 - Improved the error messages shown when JWT validation fails.
 - Improved the [`AuthTokenBuilder`](https://help.sap.com/doc/e95b7f89bb45412b943760333df7a016/1.0/en-US/index.html?com/sap/cloud/sdk/cloudplatform/security/AuthTokenBuilder.html) so that public keys used for verification of authorization tokens created by it are now being cached.
 - Client Library for SCP Workflow:
-
   - Method names improved to better reflect the Workflow domain
   - Methods return strong return types, the previous version had generic return types
   - Parameter names improved to better reflect their semantics
@@ -324,9 +321,7 @@ Release date: July 16, 2020
 - A new, experimental API to run generic OData batch requests via `ODataRequestBatch` in version agnostic module `odata-client`.
   It allows for batching entity read and modification requests. Modifications are grouped within changesets and, depending on the service implementation, they are expected to rollback if one change in the set was unsuccessful. Multiple changesets and read requests can be attached.
   The class supports entity request handling for _create_, _read_, _update_ and _delete_, as well as service specific _functions_ and _actions_.
-
   - Notes
-
     - The API is not considered final yet. The class is `@Beta` annotated. Please refrain from using it in productive application code.
     - There are no helper methods on the result object yet to conveniently parse the multipart response. However the `HttpResponse` object can be accessed already.
     - The order of method invocations matters. It defines how the individual requests are serialized, when constructing the multipart batch request.
@@ -398,9 +393,7 @@ Release date: July 16, 2020
 
 - New builder pattern for type `Resilience4jDecorationStrategy` to enable custom function decoration properties.
 - A new, experimental interface `ServiceWithNavigableEntities` for OData v4 VDM, to allow for recursive traversal of navigation properties in entity sets. This generic type offers type-safe methods to create a request along chained entities with their navigation properties. By delegating to the existing request builder classes, the interface supports all basic CRUD operations, plus count. You can use all existing request modifiers, e.g. _filter_ or _select_ statements in _Read_. The interface type is `@Beta` annotated to declare methods and sub-types are still open for changes in the future.
-
   - Example
-
     - Create a new Trip in Vacation (id 2020) of Person (username "John")
     - HTTP request: `POST /ODataService/People('John')/Vacations(2020)/Trips`
     - Sample code:
@@ -448,7 +441,6 @@ Release date: July 16, 2020
 ### New Functionality
 
 - Introducing the client library for the Workflow API on SAP Cloud Platform, Cloud Foundry
-
   - Example usage:
 
   ```
@@ -468,7 +460,6 @@ Release date: July 16, 2020
   ```
 
 - New VDM request builder for OData v4 to fetch the count of entries in an entity collection endpoint. The result is a non-null Long, the number of matching entries according to optional filter and search expressions.
-
   - Example for the VDM usage:
 
     ```
@@ -492,7 +483,6 @@ Release date: July 16, 2020
   - Note: Regenerate the VDM to enable these features on your classes.
 - The VDM request builders for OData v4 to delete and update entities `DeleteRequestBuilder` and `UpdateRequestBuilder`
   allow to influence the submission of the version identifier (ETag) of the respective entity in the remote system.
-
   - The method `disableVersionIdentifier` allows to avoid that the request header `If-Match` is sent at all.
   - The method `matchAnyVersionIdentifier` allows to control that the request header `If-Match` is sent with the value `*`.
   - Note that if both methods are invoked on the same request builder, the latest invocation takes precedence.
@@ -631,7 +621,6 @@ Release date: July 16, 2020
   ```
 
 - Update Dependencies
-
   - Update Java JWT from `3.10.0` to `3.10.1`
   - Update Mockito from `3.3.0` to `3.3.1`
   - Update Wiremock from `2.26.2` to `2.26.3`
@@ -700,7 +689,6 @@ Release date: July 16, 2020
 ### Compatibility Notes
 
 - Use the library [XSUAA Token Client and Token Flow API](https://github.com/SAP/cloud-security-xsuaa-integration/tree/master/token-client) for handling communication with [XSUAA](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/ea0281368f11472b8d2b145a2a28666c.html) service instances.
-
   - If you mock XSUAA service requests in your tests, some assertions might need to be updated. When using the new library, XSUAA request parameters should be passed as _HTTP body content_ instead of query arguments.
   - The internally used types `SubdomainReplacer` and `DefaultSubdomainReplacer` became obsolete and were removed. The usage of this classes was replaced by the new library.
   - The behavior of following methods in the utility class `XsuaaService` has been changed.

diff --git a/docs-java_versioned_docs/version-v3/release-notes/release-notes-30-to-44.mdx b/docs-java_versioned_docs/version-v3/release-notes/release-notes-30-to-44.mdx
@@ -214,7 +214,6 @@ The collection of released SAP S/4HANA Cloud client libraries from the SAP Cloud
 - The OData v4 type-safe client (VDM) generator now generates static fields for accessible properties on `VdmComplex` types, which can be used exactly like their counterparts on `VdmEntity` when building OData queries.
 - You can clear the cache for remote functions with the new experimental APIs `RemoteFunctionCache.clearCache(Destination)`
   and `RemoteFunctionCache.clearCache(Destination, functionName)`.
-
   - Example usages:
 
   ```java
@@ -262,7 +261,6 @@ The collection of released SAP S/4HANA Cloud client libraries from the SAP Cloud
 As part of the update of the pregenerated type-safe client for SAP S/4HANA On-premise, we encountered the following changes:
 
 - The following methods of the OData v4 service `ContractAccountingBusinessPartnerPaymentService` have been renamed:
-
   - `getAllBusPartPaymentParameters` has been renamed to `getAllBusPartPayment`
   - `countBusPartPaymentParameters` has been renamed to `countBusPartPayment`
   - `getBusPartPaymentParametersByKey` has been renamed to `getBusPartPaymentByKey`
@@ -271,7 +269,6 @@ As part of the update of the pregenerated type-safe client for SAP S/4HANA On-pr
   - `getBusPartPaymentItemParametersByKey` has been renamed to `getBusPartPaymentItemByKey`
 
 - The following classes of the OData v4 VDM have been renamed:
-
   - `ProtocolQueryReadSingle` has been renamed to `ProtocolQueryRead`
   - `StructuredPropertyCollection` has been renamed to `NavigationPropertyCollection`
   - `StructuredPropertyCollectionQuery` has been renamed to `NavigationPropertyCollectionQuery`
@@ -360,7 +357,6 @@ As part of the update of the pregenerated type-safe client for SAP S/4HANA On-pr
 - As part of the update of the OData VDM to SAP S/4HANA Cloud 2102 a few operations were removed.
   The operations were never supported by the SAP S/4HANA system (like CRUD support for some entities), so no existing functionality is affected.
   The following services are affected:
-
   - _Nota Fiscal – Create, Update_ - `API_LOGBR_NOTAFISCAL_SRV`
 
   - _Purchase Contracts_ - `API_PURCHASECONTRACT_PROCESS_SRV`
@@ -555,7 +551,6 @@ As part of the update of the pregenerated type-safe client for SAP S/4HANA On-pr
 ### Compatibility Notes
 
 - We removed the following dependencies from the SAP Cloud SDK Bill-of-Material (BOM):
-
   - Netty
   - Protobuf
   - Spring Security OAuth
@@ -658,7 +653,6 @@ As part of the update of the pregenerated type-safe client for SAP S/4HANA On-pr
   However, outgoing requests will always use the notation that is compatible with Version `4.0.0` of the standard for now to ensure server compatibility.
 - The Workflow API client library in module `scp-workflow-cf` was enhanced with the latest Workflow API features.
 - The CSRF token retrieval of OData v2 type-safe function imports has been improved:
-
   - Function imports using the HTTP method GET no longer issue the unnecessary CSRF token request
   - Function imports using the HTTP method POST can be processed even if the CSRF token retrieval fails (for example, if the server does not support CSRF tokens)
 
@@ -779,7 +773,6 @@ Iterable<List<EntityT>> lazyPages = request.iteratingPages().execute( destinatio
 - The method [`withHeader()`](https://help.sap.com/doc/f8a1835a26b848f69536b34bf46eeb93/1.0/en-US/com/sap/cloud/sdk/datamodel/odatav4/core/RequestBuilder.html#withHeader-java.lang.String-java.lang.String-) of OData V4 request builders is no longer experimental.
 
 - Improve the class hierarchy of [`ODataException`](https://help.sap.com/doc/f8a1835a26b848f69536b34bf46eeb93/1.0/en-US/index.html?com/sap/cloud/sdk/datamodel/odata/client/exception/ODataException.html):
-
   - Declare all subclasses as stable API
   - Merge `ODataResponseErrorException` into [`ODataServiceErrorException`](https://help.sap.com/doc/f8a1835a26b848f69536b34bf46eeb93/1.0/en-US/index.html?com/sap/cloud/sdk/datamodel/odata/client/exception/ODataServiceErrorException.html)
   - Rename `ODataServiceErrorRoot` to [`ODataServiceError`](https://help.sap.com/doc/f8a1835a26b848f69536b34bf46eeb93/1.0/en-US/index.html?com/sap/cloud/sdk/datamodel/odata/client/exception/ODataServiceError.html)
-Original file line number
+Diff line change
@@ Expand Up / @@ -148,7 +148,6 @@ cf restart app-name @@
     ```
     - Inspect the value of the entry `connectivity` of your `VCAP_SERVICES` and take note of the values of the fields
       - `credentials.onpremise_proxy_port` (we will refer to the value as _proxy-port_ hereafter)
       - `credentials.onpremise_proxy_host` (we will refer to the value as _proxy-host_ hereafter)
@@ Expand Down @@