Prepare April release

.github/CODEOWNERS

@@ -1,9 +1,11 @@
 # This files defines code ownership.
+# We start with defining ownership globally and later on can get more granular.
 
 # General content
 * @renejeglinsky
-node.js/ @smahati
-java/ @smahati
+
+node.js/ @smahati @renejeglinsky
+java/    @smahati @renejeglinsky
 
 # Infra
 .github/    @chgeo @swaldmann

.vitepress/config.js

@@ -124,8 +124,8 @@ const siteURL = new URL(process.env.SITE_HOSTNAME || 'http://localhost:4173/docs
 if (!siteURL.pathname.endsWith('/'))  siteURL.pathname += '/'
 config.themeConfig.capire = {
   versions: {
-    java_services: '4.8.0',
-    java_cds4j: '4.8.0',
+    java_services: '4.9.0',
+    java_cds4j: '4.9.0',
     cloud_sec_ams: '3.8.0'
   },
   gotoLinks: [],

.vitepress/languages/index.ts

@@ -5,7 +5,7 @@ import scsv from './scsv.tmLanguage.json' with {type:'json'}
 
 import type { LanguageInput } from 'shiki'
 export default [
-  { ...cds, aliases:['cds','dcl', 'cql'] },
+  { ...cds, aliases:['cds','cdl','dcl','cql'] },
   { ...csv, aliases:['csv','csvc'] },
   { ...scsv, aliases:['csvs'] },
   { ...log, aliases:['log','logs'] },

.vitepress/theme/components/ConfigInspect.vue

@@ -4,7 +4,7 @@
   >
   <!-- :hideTriggers="[]" :shown="true" -->
 
-    <a class="cfg vp-doc"><code class="cfg">{{ label }}</code></a>
+    <a class="cfg vp-doc"><span class="cfg">{{ label }}</span></a>
 
     <template #popper>
       <div class="vp-code-group vp-doc" v-if="java">
@@ -16,32 +16,34 @@
       <div class="vp-code-group vp-doc" v-else>
         <CodeGroup :groups="[
           { id: 'pkg-rc',   label: 'package.json',   lang: 'json',       group, code: pkgStr },
-          { id: 'pkg-priv', label: '~/.cdsrc.json',  lang: 'json',       group, code: rcJsonStr, private: true },
-          { id: 'pkg',      label: '.cdsrc.json',    lang: 'json',       group, code: rcJsonStr },
+          // { id: 'pkg-priv', label: '~/.cdsrc.json',  lang: 'json',       group, code: rcJsonStr, private: true },
+          // { id: 'pkg',      label: '.cdsrc.json',    lang: 'json',       group, code: rcJsonStr },
           { id: 'js',  label: '.cdsrc.js',           lang: 'js',         group, code: rcJsStr },
           { id: 'yml', label: '.cdsrc.yaml',         lang: 'yml',        group, code: rcYmlStr },
           { id: 'env', label: '.env file',           lang: 'properties', group, code: propStr },
-          { id: 'shl', label: 'Linux/macOS Shells',  lang: 'sh',         group, code: 'export '+envStr, transient: true },
-          { id: 'shp', label: 'Powershell',          lang: 'powershell', group, code: '$Env:'+envStr, transient: true },
-          { id: 'shw', label: 'Cmd Shell',           lang: 'cmd',        group, code: 'set '+envStr, transient: true }
+          // { id: 'shl', label: 'Linux/macOS Shells',  lang: 'sh',         group, code: 'export '+envStr, transient: true },
+          // { id: 'shp', label: 'Powershell',          lang: 'powershell', group, code: '$Env:'+envStr, transient: true },
+          // { id: 'shw', label: 'Cmd Shell',           lang: 'cmd',        group, code: 'set '+envStr, transient: true }
         ]" />
       </div>
     </template>
   </VDropdown>
-  <code class="cfg" v-else>{{ label }}</code> <!-- intermediate fallback -->
+  <span class="cfg" v-else>{{ label }}</span> <!-- intermediate fallback -->
 </template>
 
 <script setup lang="ts">
   import { defineComponent, h, onMounted, ref, useSlots } from 'vue'
   import FloatingVue from 'floating-vue'
   import yaml from 'yaml'
 
-  const { java, keyOnly, filesOnly, showPrivate, label:labelProp, keyDelim } = defineProps<{
+  const { value, java, keyOnly, filesOnly, showPrivate, section, label:labelProp, keyDelim } = defineProps<{
     java?: boolean,
     keyOnly?: boolean,
     filesOnly?: boolean,
     showPrivate?: boolean,
+    section?: string,
     label?: string,
+    value?: string,
     keyDelim?: string
   }>()
 
@@ -84,8 +86,8 @@
   const slots = useSlots()
   const slotVal = slots.default?.().at(0)?.children?.toString().trim() ?? 'error: provide <Config>your_key:value</Config>'
 
-  const [key, val] = slotVal.split(/\s*[:=]\s*(.*)/) // split on first `:` or `=`
-  const label = labelProp || `${keyOnly ? key: slotVal}`
+  const [key, val = value] = slotVal.split(/\s*[:=]\s*(.*)/) // split on first `:` or `=`
+  const label = labelProp || ( keyOnly ? key : slotVal )
   const keyDel = keyDelim ?? '.'
 
   const cfgKey = ref()
@@ -102,28 +104,26 @@
 
   onMounted(() => {
     popperVisible.value = true
+    const fqn = (section ? section + keyDel : '') + key
+    cfgKey.value = fqn
+    let value:any = !val ? '...'
+    : val === 'true' ? true
+    : val === 'false' ? false
+    : val === 'null' ? null
+    : Number(val) || val
 
-    cfgKey.value = key
-    let value:any = val
-    if (val === 'true')  value = true
-    else if (val === 'false')  value = false
-    else if (val === 'null')  value = null
-    else if (parseInt(val).toString() === val)  value = parseInt(val)
-    else if (parseFloat(val).toString() === val)  value = parseFloat(val)
-    else if (!val)  value = '…'
-
-    group.value = 'group-'+key
+    group.value = 'group-'+fqn
 
     let jsonVal
     if (typeof value === 'string' && value.trim().match(/^[[{].*[\]}]$/)) { try { jsonVal = JSON.parse(value) } catch {/*ignore*/ } }
-    const pkg = toJson(key, jsonVal ?? value, keyDel)
+    const pkg = toJson(fqn, jsonVal ?? value, keyDel)
 
     pkgStr.value = JSON.stringify(pkg, null, 2)
     rcJsonStr.value = JSON.stringify(pkg.cds??{}, null, 2)
     rcJsStr.value = 'module.exports = ' + rcJsonStr.value.replace(/"(\w*?)":/g, '$1:')
     rcYmlStr.value = yaml.stringify(pkg.cds)
 
-    let envKey = key.replaceAll('_', '__').replaceAll(keyDel, '_')
+    let envKey = fqn.replaceAll('_', '__').replaceAll(keyDel, '_')
     if (/^[a-z_]+$/.test(envKey)) envKey = envKey.toUpperCase() // only uppercase if not camelCase
     envStr.value = `${envKey}=${jsonVal ? JSON.stringify(jsonVal) : value}`
     propStr.value = `${envKey}=${jsonVal ? JSON.stringify(jsonVal) : value}`
@@ -148,23 +148,15 @@ function toJson(key:string, value:string, delim:string): Record<string, any> {
   .v-popper--theme-cfgPopper .v-popper__inner {
     background-color: var(--vp-code-block-bg) !important;
   }
-  code.cfg::after {
-    content: " ⛭";
-  }
 </style>
 
 <style scoped>
   .v-popper {
     display: inline;
   }
   a.cfg {
-    color: var(--vp-c-text-1);
-    text-decoration:none;
-  }
-  a.cfg:hover {
-    text-decoration:none;
-  }
-  a.cfg:active {
-    text-decoration:none;
+    color: var(--vp-c-brand-1);
+    font-style: italic;
+    text-decoration: underline dashed 0.5px;
   }
 </style>

.vitepress/theme/components/cds-playground/LiveCode.vue

@@ -219,7 +219,7 @@ onMounted(() => { metaKey.value = /(Mac|iPhone|iPad)/i.test(navigator?.userAgent
 
 .editor-row .editor {
   flex: 1;
-  min-width: 0;
+  min-width: 0 !important;
 }
 
 .editor {

.vitepress/theme/styles.scss

@@ -44,6 +44,7 @@ html {
   --vp-c-brand-soft: rgba(16, 179, 185, 0.16);
 
   &.dark {
+    --vp-c-text-1: #eed;
     --vp-c-brand-1: var(--vp-c-yellow-2);
     --vp-c-brand-2: var(--vp-c-yellow-2);
     --vp-c-brand-3: var(--vp-c-yellow-3);
@@ -388,7 +389,7 @@ img, video.bright {
         }
       }
 
-      // reposition indicators to keep within padding 
+      // reposition indicators to keep within padding
       .item > .indicator { left: -14px;  }
       // also enable indicators for level-1 items
       &.level-1.is-active > .item > .indicator {
@@ -434,22 +435,22 @@ footer {
 
 /* expand width on big screens */
 @media screen and (min-width: 1600px) {
-  div[class*='language-']:hover,
-  div[class*='language-']:focus,
-  pre.log:hover,
-  pre.log:focus {
+  :not(.no-wide) > div[class*='language-']:hover,
+  :not(.no-wide) > div[class*='language-']:focus,
+  :not(.no-wide) > pre.log:hover,
+  :not(.no-wide) > pre.log:focus {
     min-width: fit-content;
     padding-right: 40px;
     z-index: 1; position: relative; // draw over outline
   }
-  table:hover,
-  table:focus {
+  :not(.no-wide) > table:hover,
+  :not(.no-wide) > table:focus {
     min-width: fit-content;
   }
-  tr {
+  :not(.no-wide) > tr {
     z-index: 1; position: relative;  // draw wide rows over outline
   }
-  [class*='language-'] pre {
+  :not(.no-wide) > [class*='language-'] pre {
     overflow: hidden !important;
   }
   // expand navbar to cover wide content (see java/development/properties)

cds/annotations.md

@@ -18,10 +18,10 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/
 
 ## General Purpose
 
-| Annotation     | Description | Alternatives       |
-|----------------|-------------|--------------------|
-| `@title`       |             | `Common.Label`     |
-| `@description` |             | `Core.Description` |
+| Annotation     | Description | Alternatives        |
+|----------------|-------------|---------------------|
+| `@title`       |             | `@Common.Label`     |
+| `@description` |             | `@Core.Description` |
 
 
 ## Access Control

cds/cdl.md

@@ -283,7 +283,7 @@ CDL supports line-end, block comments, and *doc* comments as in Java and JavaScr
 /** doc comment */
 ```
 
-#### Doc Comments {#doc-comment}
+#### Doc Comments 
 
 A multi-line comment of the form `/** … */` at an [annotation position](#annotation-targets) is considered a *doc comment*:
 
@@ -1236,7 +1236,7 @@ entity Foo @(
 entity Foo { /* elements */ }
 ```
 
-For an `@inner` annotation, only the syntax `@(...)` is available.
+For annotations at the `@inner` position, only the syntax `@(...)` is available.
 
 
 #### Using `annotate` Directives

cds/compiler/hdbcds-to-hdbtable.md

@@ -120,7 +120,7 @@ In contrast to the `hdbtable` plugin, the `hdbcds` plugin is able to handle remo
 
 ## Multiline Doc Comments
 
-This is only relevant if you have switched on [Doc Comments](../../cds/cdl#doc-comment)
+This is only relevant if you have switched on [Doc Comments](../../cds/cdl#doc-comments)
 and if you have enabled translation of doc comments to the `COMMENT` feature in the database.
 
 Doc comments can span across multiple lines:

cds/types.md

@@ -30,7 +30,7 @@ ANSI SQL types, when deployed to a relational database (concrete mappings to spe
 | `Timestamp`         | _µs_ precision, with up to 7 fractional digits                         | _TIMESTAMP_    |
 | `String` (`length`) | Default *length*: 255; on HANA: 5000                                   | _NVARCHAR_     |
 | `Binary` (`length`) | Default *length*: 255; on HANA: 5000                                   | _VARBINARY_    |
-| `Vector` (`length`) | SAP HANA Cloud QRC 1/2024, or later only                               | _REAL_VECTOR_  |
+| `Vector` (`length`) | for Vector Embeddings [-> see notes below](#vector-embeddings)                                                  | ( _DB-specific_ )  |
 | `LargeBinary`       | Unlimited binary data, usually streamed at runtime                     | _BLOB_         |
 | `LargeString`       | Unlimited textual data, usually streamed at runtime                    | _NCLOB_        |
 | `Map`               | Mapped to *NCLOB* for HANA.                                            | *JSON* type    |
@@ -40,6 +40,10 @@ ANSI SQL types, when deployed to a relational database (concrete mappings to spe
 > <Config> cds.cdsc.defaultStringLength = 255 </Config> and <br/>
 > <Config> cds.cdsc.defaultBinaryLength = 255 </Config>.
 
+###### Vector Embeddings
+> [!info] Vector Embeddings
+> The `Vector` type is used for vector embeddings, which are a way to represent data (like text, images, etc.) as high-dimensional vectors. Requires SAP HANA Cloud QRC 1/2024, or later, [`@sap/cds` v9.9+](/releases/2026/apr26), and [CAP Java v4.9+](/releases/2026/apr26) to use with H2 or SQLite.
+
 > [!tip] Use Attachments instead of LargeBinary
 > Consider using _Attachments_, as provided through [the CAP Attachments plugins](../plugins/index#attachments), instead of `LargeBinary` types for user-generated content like documents, images, etc.
 

eslint.config.mjs

@@ -1,5 +1,4 @@
 import cds from '@sap/cds/eslint.config.mjs'
-import vue from 'eslint-plugin-vue'
 import globals from 'globals'
 
 export default [
@@ -11,20 +10,15 @@ export default [
     ],
   },
   ...cds.recommended,
-  ...vue.configs['flat/essential'],
   {
-    files: ['*.vue', '**/*.vue', '**/*.js'],
+    files: ['**/*.js'],
     languageOptions: {
       parserOptions: {
         parser: '@typescript-eslint/parser'
       },
       globals: {
         ...globals.browser
       }
-    },
-    rules: {
-      'vue/multi-word-component-names': 0,
-      'vue/no-v-text-v-html-on-component': 0
     }
   }
 ]

get-started/get-help.md

@@ -529,6 +529,35 @@ This error occurs if all of the following applies:
 | _Root Cause_ | The name/prefix of the native SAP HANA object collides with a name/prefix in the CAP CDS model.                                                                                                                                                                                                                                                                                                  |
 | _Solution_   | Change the name of the native SAP HANA object so that it doesn't start with the name given in the error message and doesn't start with any other prefix that occurs in the CAP CDS model. If you can't change the name of the SAP HANA object, because it already exists, define a synonym for the object. The name of the synonym must follow the naming rule to avoid collisions (root cause). |
 
+#### Deployment fails — _The include_filter definitions ... use key values that are not disjunct_
+
+|              | Explanation                             |
+|--------------|----------------------------|
+| _Root Cause_ | You have changed from data files like `xxx_texts.csv` to `xxx_texts_de.csv`. |
+| _Solution_   | Add entries in `undeploy.json`. |
+
+
+If you've already deployed your application using translation files _without_ language key like `xxx_texts.csv` and now want to use language-specific translation files like `xxx_texts_de.csv`, you have to **undeploy the existing translation files**.
+
+Add the corresponding file entries, for example
+```json
+[
+  ...
+  "src/gen/data/xxx_texts.hdbtabledata",
+  "src/gen/data/xxx_texts.csv"
+]
+```
+to your _undeploy.json_.
+
+Otherwise, you will get a deployment error similar to this one:
+
+```
+The include_filter definitions in the table import files .../xxx_texts.hdbtabledata
+and .../xxx_texts_de.hdbtabledata use key values that are not disjunct;
+.../xxx_texts.hdbtabledata defines no include_filters which prohibits other imports
+from importing into the same table.
+```
+
 
 ### Why is removed sample _.csv_ deployed and overwriting existing data? { #hana-csv}
 
@@ -660,7 +689,14 @@ See [How to configure your App Router](../guides/extensibility/customization#app
 
 [Find the documentation on `cds login`](../guides/extensibility/customization#cds-login){.learn-more}
 
-<div id="hana-tms-errors" />
+### Why does my subscription fail with "Subaccount verification failed"
+
+When using HANA TMS v2, the message "Subaccount verification failed" indicates that you are trying to create a tenant container for a HANA tenant that was created in a different subaccount.
+
+Most probably, you are using the same `hana_tenant_prefix` and `tenant_id` as another application that has been deployed in another subaccount.
+
+See how to [handle HANA tenants with HANA TMS v2](/@external/guides/multitenancy/index.md#handle-sap-hana-tenants) to avoid this situation.
+
 
 ## BTP