Bump @sap-cloud-sdk/util from 3.9.0 to 3.10.0

[dependabot[bot]]

Bumps @sap-cloud-sdk/util from 3.9.0 to 3.10.0.

Release notes

Sourced from @​sap-cloud-sdk/util's releases.

v3.10.0

Compatibility Notes

• [connectivity] The SAP Cloud SDK used to get all subaccount and instance destinations, that are available with your JWT (without potentially required token retrieval), through two requests to the destination service (/subaccountDestinations and /instanceDestinations). While this approach can have advantages when caching, it can cause severe performance issues without caching. Therefore, from now on, only one destination is retrieved per requested destination through /destinations. You can no longer rely on the SDK to automatically cache all destinations on the first request. If needed, you can call getAllDestinationsFromDestinationService() with cache enabled instead. (c721bbd)
• [connectivity] Using Principal Propagation through authentication type NoAuthentication is no longer supported. This resulted in erroneous behavior for destinations with authentication type NoAuthentication. If you need to use Principal Propagation use authentication type PrincipalPropagation. (28c9cb7)

New Functionalities

• [util] Add support for setting log level for newly created logger using environment variable SAP_CLOUD_SDK_LOG_LEVEL. (4d2b49b)

Improvements

• [connectivity] Retrieve only one destination per requested destination instead of all subaccount and instance destinations. (See compatibility notes.) (c721bbd)

Fixed Issues

• [connectivity] Allow the use of authentication type NoAuthentication with proxy type OnPremise without requiring the SAP-Connectivity-Authentication header. (28c9cb7)

Changelog

Sourced from @​sap-cloud-sdk/util's changelog.

3.10.0

API Docs: https://sap.github.io/cloud-sdk/api/3.10.0

Compatibility Notes

• [connectivity] The SAP Cloud SDK used to get all subaccount and instance destinations, that are available with your JWT (without potentially required token retrieval), through two requests to the destination service (/subaccountDestinations and /instanceDestinations). While this approach can have advantages when caching, it can cause severe performance issues without caching. Therefore, from now on, only one destination is retrieved per requested destination through /destinations. You can no longer rely on the SDK to automatically cache all destinations on the first request. If needed, you can call getAllDestinationsFromDestinationService() with cache enabled instead. (c721bbd)
• [connectivity] Using Principal Propagation through authentication type NoAuthentication is no longer supported. This resulted in erroneous behavior for destinations with authentication type NoAuthentication. If you need to use Principal Propagation use authentication type PrincipalPropagation. (28c9cb7)

New Functionalities

• [util] Add support for setting log level for newly created logger using environment variable SAP_CLOUD_SDK_LOG_LEVEL. (4d2b49b)

Improvements

• [connectivity] Retrieve only one destination per requested destination instead of all subaccount and instance destinations. (See compatibility notes.) (c721bbd)

Fixed Issues

• [connectivity] Allow the use of authentication type NoAuthentication with proxy type OnPremise without requiring the SAP-Connectivity-Authentication header. (28c9cb7)

Commits

• 5a1fb9a v3.10.0
• d63e8d6 chore(deps-dev): bump @​sap/cds from 6.8.4 to 7.5.1 (#4397)
• bda6a71 chore(deps-dev): bump turbo from 1.11.2 to 1.11.3 (#4396)
• c68fe54 chore(deps): bump axios from 1.6.3 to 1.6.4 (#4395)
• 374ac10 chore(deps-dev): bump puppeteer from 21.6.1 to 21.7.0 (#4394)
• 1793dde chore(deps-dev): bump tsd from 0.30.1 to 0.30.3 (#4393)
• 6d8b2f2 chore(deps-dev): bump @​typescript-eslint/eslint-plugin (#4389)
• bf5ca65 chore(deps-dev): bump @​typescript-eslint/parser from 6.16.0 to 6.17.0 (#4388)
• b344e5a chore(deps-dev): bump eslint-plugin-jest from 27.6.0 to 27.6.1 (#4387)
• 5a79f49 chore(deps): bump tj-actions/changed-files in /.github/workflows (#4391)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)