Merlin Beutlberger

Thanks for reporting. This looks like what we call a "Partial Deprecation" (see also https://github.com/SAP/ui5-linter/pull/286). We'll look into how best to solve this.

> Will be implemented in CPOUI5FOUNDATION-990. Note: Since the mentioned API is currently not detected as a problem by UI5 linter, we decided to move the implementation of a detection,...

> Will be implemented in CPOUI5FOUNDATION-990. Note: Since the mentioned API is currently not detected as a problem by UI5 linter, we decided to move the implementation of a detection,...

Once we make the UI5 version and -framework configurable, this should be solved. Then, only if the SAPUI5 framework is used, the SAPUI5 types are installed.

Rebased, snapshots updated (using `npm run unit-update-snapshots`), commit message and eslint errors resolved + minor readme update 👍 Let's get a review from UA and from another developer of the...

Sorry to bother you @marianfoo, but since we moved the repository to a new organization, you'll need to sign the CLA again (see comment above)

> Will be implemented in CPOUI5FOUNDATION-990. Note: Since the mentioned API is currently not detected as a problem by UI5 linter, we decided to move the implementation of a detection,...

To verify the shrinkwrap: ```sh npm i cd packages/cli node ../../internal/shrinkwrap-extractor/cli.js ../../ rm -rf node_modules # Delete node_modules within CLI package # npm ci --workspaces false ``` Before Matthias' fix...

> I suspect there might still be a problem with dependencies hoisted to the workspace root for packages other than the CLI, conflicting with dependencies of the CLI. I added...

Please share the output of running the following two commands: * To retrieve the UI5 Tooling version: `npm run deploy -- --version` (should be similar to `ui5 --version` * To...