September Release (#2141)

Co-authored-by: BraunMatthias <59841349+BraunMatthias@users.noreply.github.com>
Co-authored-by: matthia.braun@sap.com <matthias@W-5CG3323MK3>
Co-authored-by: Mahati Shankar <93712176+smahati@users.noreply.github.com>
Co-authored-by: Marc Becker <marc.becker@sap.com>
Co-authored-by: ecklie <52252271+ecklie@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: chgeo <7470719+chgeo@users.noreply.github.com>
Co-authored-by: Christian Georgi <christian.georgi@sap.com>
Co-authored-by: Daniel O'Grady <daniel.o-grady@sap.com>
Co-authored-by: Daniel O'Grady <103028279+daogrady@users.noreply.github.com>
Co-authored-by: Christian Georgi <chgeo@users.noreply.github.com>
Co-authored-by: Steffen Waldmann <steffen.waldmann@sap.com>
Co-authored-by: sjvans <30337871+sjvans@users.noreply.github.com>
Co-authored-by: Johannes Vogel <31311694+johannes-vogel@users.noreply.github.com>
Co-authored-by: Adrian Görler <adrian.goerler@sap.com>
Co-authored-by: Dr. David A. Kunz <david.kunz@sap.com>
Co-authored-by: Daniel Hutzel <daniel.hutzel@sap.com>
Co-authored-by: Dietrich Mostowoj <34100436+dimamost@users.noreply.github.com>
Co-authored-by: Evgeny Andreev <eugene.andreev@gmail.com>
Co-authored-by: Johannes Vogt <j.vogt@sap.com>
Co-authored-by: Matthias Schur <107557548+MattSchur@users.noreply.github.com>
Co-authored-by: Markus Ofterdinger <markus.ofterdinger@sap.com>

Author: 21 people

.github/eslint-plugin/index.js

@@ -10,19 +10,15 @@
 import * as fs from 'node:fs'
 import * as path from 'node:path'
 
-const RULES_BASE_PATH = path.join('tools', 'cds-lint', 'rules');
-const EXAMPLES_BASE_PATH = path.join('tools', 'cds-lint', 'examples');
+const RULES_BASE_PATH    = path.join(import.meta.dirname, '../../tools/cds-lint/rules');
+const EXAMPLES_BASE_PATH = RULES_BASE_PATH
 const MENU_FILE_NAME = '_menu.md';
 
 /**
  * Get a list of all rule description files.
  * @returns {string[]} An array of rule description file names.
  */
-const getRuleDescriptionFiles = () =>
-    fs.readdirSync(RULES_BASE_PATH)
-        .filter(file => file.endsWith('.md'))
-        .filter(file => !['index.md', MENU_FILE_NAME].includes(file))
-        .sort()
+const getRuleDescriptionFiles = () => fs.globSync(path.join(RULES_BASE_PATH, '*/index.md')).sort()
 
 /**
  * Generates the menu markdown file
@@ -33,12 +29,13 @@ const getRuleDescriptionFiles = () =>
 function generateMenuMarkdown () {
     const rules = getRuleDescriptionFiles();
     const menu = rules.map(rule => {
-        const clean = rule.replace('.md', '');
-        return `# [${clean}](${clean})`
+        const folderPath = path.posix.dirname(path.relative(RULES_BASE_PATH, rule));
+        const name = path.basename(folderPath);
+        return `# [${name}](${folderPath}/)`
     }).join('\n');
-    const menuFilePath = path.join(RULES_BASE_PATH, '_menu.md')
+    const menuFilePath = path.join(RULES_BASE_PATH, MENU_FILE_NAME)
     fs.writeFileSync(menuFilePath, menu);
-    console.info(`generated menu to ${menuFilePath}`)
+    console.info(`generated menu to ${path.relative(process.cwd(), menuFilePath)}`);
 }
 
 /**
@@ -52,11 +49,12 @@ function generateJsRuleStub (ruleName) {
         console.error('Please provide a rule name, e.g. "no-shared-handler-variables" as second argument');
         process.exit(1);
     }
-    const stubFilePath = path.join(RULES_BASE_PATH, ruleName + '.md');
+    const stubFilePath = path.join(RULES_BASE_PATH, ruleName, 'index.md');
     if (fs.existsSync(stubFilePath)) {
         console.error(`file ${stubFilePath} already exists, will not overwrite`);
         process.exit(2);
     }
+    fs.mkdirSync(path.dirname(stubFilePath), { recursive: true });
     const stub = fs.readFileSync(path.join(import.meta.dirname, 'js-rule-stub.md'), 'utf-8').replaceAll('$RULE_NAME', ruleName);
     fs.writeFileSync(stubFilePath, stub);
     console.info(`generated stub to ${stubFilePath}`);

.github/eslint-plugin/js-rule-stub.md

@@ -3,7 +3,7 @@ status: released
 ---
 
 <script setup>
-  import PlaygroundBadge from '../components/PlaygroundBadge.vue'
+  import PlaygroundBadge from '../../components/PlaygroundBadge.vue'
 </script>
 
 # $RULE_NAME
@@ -22,7 +22,7 @@ This rule was introduced in `@sap/eslint-plugin-cds x.y.z`.
 DESCRIPTION OF CORRECT EXAMPLE
 
 ::: code-group
-<<< ../examples/$RULE_NAME/correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
   name="$RULE_NAME"
@@ -35,7 +35,7 @@ DESCRIPTION OF CORRECT EXAMPLE
 DESCRIPTION OF INCORRECT EXAMPLE
 
 ::: code-group
-<<< ../examples/$RULE_NAME/incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
   name="$RULE_NAME"

.vitepress/config.js

@@ -106,8 +106,8 @@ config.rewrites = rewrites
 // Add custom capire info to the theme config
 config.themeConfig.capire = {
   versions: {
-    java_services: '4.3.1',
-    java_cds4j: '4.3.0'
+    java_services: '4.4.0',
+    java_cds4j: '4.4.1'
   },
   gotoLinks: []
 }

LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2019-2025 SAP SE
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

eslint.config.mjs

@@ -1,5 +1,6 @@
 import cds from '@sap/cds/eslint.config.mjs'
 import vue from 'eslint-plugin-vue'
+import globals from 'globals'
 
 export default [
   {
@@ -12,11 +13,14 @@ export default [
   ...cds.recommended,
   ...vue.configs['flat/essential'],
   {
-    files: ['*.vue', '**/*.vue'],
+    files: ['*.vue', '**/*.vue', '**/*.js'],
     languageOptions: {
       parserOptions: {
         parser: '@typescript-eslint/parser'
       },
+      globals: {
+        ...globals.browser
+      }
     },
     rules: {
       'vue/multi-word-component-names': 0,

get-started/troubleshooting.md

@@ -626,8 +626,7 @@ Now you can build the archive with:
 mbt build -t gen --mtar mta.tar -e less.mtaext
 ```
 
-::: warning
-This approach is only recommended
+::: warning Not recommended for production deployments
 - For test deployments during _development_.  For _production_ deployments,  self-contained archives are preferrable.
 - If all your dependencies are available in _public_ registries like npmjs.org or Maven Central.  Dependencies from _corporate_ registries are not resolvable in this mode.
 :::
@@ -768,7 +767,16 @@ If you receive an error response `404 Not Found: Requested route ('<route>') doe
 
     :::
 
+### Why do I get a _404 Cannot GET /_ error?
 
+For security reasons, the **index page is not served in production** by default in both [Node.js](../node.js/cds-server#toggle-generic-index-page) and [Java](../java/developing-applications/configuring#production-profile).
+
+If you try to access your backend URL, you will therefore see a _404 Cannot GET /_ error.
+This also means you **cannot use the `/` path as a health status indicator**.  See the [Health Checks guide](../guides/deployment/health-checks) for the correct paths.
+
+Only if absolutely required and you understand the security implications to your application, you can enable this page in your deployment.
+
+Learn more about the generic index page in [Java](../java/developing-applications/properties#cds-indexPage) and in [Node.js](../node.js/cds-server#toggle-generic-index-page).{.learn-more}
 
 ## CAP on Kyma
 

guides/databases-hana.md

@@ -9,10 +9,14 @@ status: released
 
 [SAP HANA Cloud](https://www.sap.com/products/technology-platform/hana.html) is supported as the CAP standard database and recommended for productive use with full support for schema evolution and multitenancy.
 
-::: warning
+::: warning Validation strategy
 
 CAP isn't validated with other variants of SAP HANA, like "SAP HANA Database as a Service" or "SAP HANA (on premise)".
 
+The database services are validated against the latest maintained QRC version of SAP HANA Cloud. It's not guaranteed that outdated versions are fully functional with the latest database services.
+
+[See the official SAP HANA Cloud documentation for their maintenance strategy.](https://help.sap.com/docs/HANA_CLOUD_CN/1f64fe39189f4176bf659e737d62222a/6ced4d164e234b74aa9bea82435ce9a8.html){.learn-more}
+
 :::
 
 ## Setup & Configuration
@@ -53,9 +57,6 @@ The datasource for SAP HANA is then auto-configured based on available service b
 
 :::
 
-
-
-
 ## Running `cds build`
 
 Deployment to SAP HANA is done via the [SAP HANA Deployment Infrastructure (HDI)](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-developer-guide-for-cloud-foundry-multitarget-applications-sap-business-app-studio/sap-hdi-deployer?) which in turn requires running `cds build` to generate all the deployable HDI artifacts. For example, run this in [capire/bookshop](https://github.com/capire/bookshop):
@@ -201,7 +202,7 @@ cds deploy --to hana
 Behind the scenes, `cds deploy` does the following:
 
 * Compiles the CDS model to SAP HANA files (usually in _gen/db_, or _db/src/gen_)
-* Generates _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata?)_ files for the [CSV files](databases#providing-initial-data) in the project. If a _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata?)_ file is already present next to the CSV files, no new file is generated.
+* Generates _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ files for the [CSV files](databases#providing-initial-data) in the project. If a _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ file is already present next to the CSV files, no new file is generated.
 * Creates a Cloud Foundry service of type `hdi-shared`, which creates an HDI container. Also, you can explicitly specify the name like so: `cds deploy --to hana:<myService>`.
 * Starts `@sap/hdi-deploy` locally. If you need a tunnel to access the database, you can specify its address with `--tunnel-address <host:port>`.
 * Stores the binding information with profile `hybrid` in the _.cdsrc-private.json_ file of your project. You can use a different profile with parameter `--for`. With this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
@@ -651,7 +652,7 @@ Only use CSV files for _configuration data_ that can't be changed by application
 
 :::
 
-Yet, if you need to support initial data with user changes, you can use the `include_filter` option that _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata?version=2024_1_QRC)_ offers.
+Yet, if you need to support initial data with user changes, you can use the `include_filter` option that _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ offers.
 
 
 

guides/deployment/to-cf.md

@@ -194,22 +194,20 @@ Two deployment options are available:
 
 #### Option A: SAP Cloud Portal
 
-If you intend to deploy user interface applications, you also need to set up the [HTML5 Application Repository](https://discovery-center.cloud.sap/serviceCatalog/html5-application-repository-service) in combination with the [SAP Cloud Portal service](https://discovery-center.cloud.sap/serviceCatalog/cloud-portal-service):
+If you intend to deploy **multi-tenant** user interface applications, you also need to set up the [HTML5 Application Repository](https://discovery-center.cloud.sap/serviceCatalog/html5-application-repository-service) in combination with the [SAP Cloud Portal service](https://discovery-center.cloud.sap/serviceCatalog/cloud-portal-service):
 
 ```sh
 cds add portal
 ```
 
-#### Option B: SAP Build Work Zone, Standard Edition <Beta />
+#### Option B: SAP BTP Application Frontend <Beta />
 
-For **single-tenant applications**, you can use [SAP Build Work Zone, Standard Edition](https://discovery-center.cloud.sap/serviceCatalog/sap-build-work-zone-standard-edition):
+For **single-tenant** applications, you can use the new [SAP BTP Application Frontend](https://help.sap.com/docs/application-frontend-service) service:
 
 ```sh
-cds add workzone
+cds add app-front
 ```
 
-**Important:** This also requires you to set up SAP Build Work Zone, Standard Edition [according to the SAP Learning tutorial](https://developers.sap.com/tutorials/spa-configure-workzone.html).
-
 ### 6. Optional: Multitenancy { #add-multitenancy }
 
 To enable multitenancy for production, run the following command:

guides/extensibility/composition.md

@@ -134,7 +134,7 @@ Add the dependency to the reuse package to your `pom.xml`:
 :::
 
 As Maven dependencies are - in contrast to `npm` packages - downloaded into a global cache, you need to make the artifacts from the reuse package available in your project locally.
-The CDS Maven Plugin provides a simple goal named `resolve`, that performs this task for you and extracts reuse packages into the `target/cds/` folder of the Maven project.
+The CDS Maven Plugin provides a simple goal named `resolve`, that performs this task for you and extracts reuse packages into the `target/cds/` folder of the CAP project.
 Include this goal into the `pom.xml`, if not already present:
 
 ::: code-group

guides/multitenancy/index.md

@@ -175,12 +175,18 @@ cds add multitenancy
      "devDependencies": {
        "@cap-js/sqlite": "^2"
      },
+     "engines": {
+       "node": ">=20"
+     },
      "scripts": {
        "start": "cds-serve",
        "build": "cds build ../.. --for mtx-sidecar --production && npm ci --prefix gen"
      },
      "cds": {
-       "profile": "mtx-sidecar"
+       "profiles": [
+         "mtx-sidecar",
+         "java"
+       ]
      }
    }
    ```
@@ -772,6 +778,13 @@ cds up --to k8s
 
 :::
 
+:::tip Ensure a unique metadata container
+To prevent potential conflicts during the initial creation of the MTXS metadata container (`t0`), it is recommended to perform the initial deployment with only one instance of the MTXS sidecar.
+
+Alternatively, you can run `cds-mtx upgrade t0` beforehand, such as in a [Cloud Foundry hook](#run-as-cloud-foundry-hook).
+:::
+
+
 ### Subscribe
 
 **Create a BTP subaccount** to subscribe to your deployed application. This subaccount has to be in the same region as the provider subaccount, for example, `us10`.
@@ -980,6 +993,8 @@ cds watch --profile dev
 
 :::
 
+<div id="hana-tms" />
+
 ## SaaS Dependencies {#saas-dependencies}
 Some of the xsuaa-based services your application consumes need to be registered as _reuse services_ to work in multitenant environments. This holds true for the usage of both the SaaS Registry service and the Subscription Manager Service (SMS).