September release 2026

.github/CODEOWNERS

@@ -2,11 +2,11 @@
 # We start with defining ownership globally and later on can get more granular.
 
 # General content
-* @smahati @danjoa
+*  @renejeglinsky @danjoa
 
-node.js/ @smahati @danjoa
-java/    @smahati @danjoa
-tools/   @chgeo @swaldmann @smahati
+node.js/ @smahati @renejeglinsky @danjoa
+java/    @smahati @renejeglinsky @danjoa
+tools/   @chgeo @swaldmann @renejeglinsky
 
 # Infra
 .github/    @chgeo @swaldmann

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

@@ -18,7 +18,7 @@ This rule was introduced in `@sap/eslint-plugin-cds x.y.z`.
 DESCRIPTION OF CORRECT EXAMPLE
 
 ::: code-group
-<<< correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< correct/srv/admin-service.js{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
   name="$RULE_NAME"
@@ -31,7 +31,7 @@ DESCRIPTION OF CORRECT EXAMPLE
 DESCRIPTION OF INCORRECT EXAMPLE
 
 ::: code-group
-<<< incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< incorrect/srv/admin-service.js{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
   name="$RULE_NAME"

.github/etc/blc.js

@@ -56,6 +56,8 @@ const urlExcludesPublicRepo = [
     /\/releases/,
     /\/resources/,
     /cds\/compiler\/messages/,
+    /cds\/cdl/,
+    /cds\/types/,
     /mcp/
 ]
 

.hyperspace/pull_request_bot.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://devops-insights-pr-bot.cfapps.eu10-004.hana.ondemand.com/schema/pull_request_bot.json",
+  "features": {
+    "control_panel": true,
+    "summarize": {
+      "auto_generate_summary": false,
+      "auto_insert_summary": false
+    },
+    "review": {
+      "auto_generate_review": false,
+      "use_custom_review_focus": true
+    }
+  }
+}

.hyperspace/pull_request_bot_review_focus.md

@@ -0,0 +1,88 @@
+---
+description: 'Does a detailed edit on the current file(s).'
+tools: ['read', 'agent', 'edit', 'todo', 'search']
+---
+
+### ROLE
+You are a helpful editor for a technical writer. Your task is to review and improve the text while ensuring that it adheres to a structured set of writing rules. All categories are of equal priority—no rule should be prioritized over another.
+
+DO:
+- Read the whole file
+- Only provide suggestions on the diff in the PR.
+
+DON'T:
+- Provide suggestion on content that has not been changed in this Pull Request.
+
+### TASK
+Perform a structured review of the text, checking compliance with the following categories:
+
+1. Grammar & Style
+-  Use U.S. English spelling and punctuation.
+-  Prefer active voice and present tense.
+-  Allow passive voice only when explaining a system process.
+-  Use common contractions, but avoid them in warnings or important messages.
+-  Use colons, parentheses, question marks, and intensifiers judiciously.
+-  Avoid exclamation marks, and abbreviations.
+- Use a colon (:) to introduce information. If the colon is followed by an incomplete sentence, begin the first word after the colon with a lowercase letter.
+- Spell out numbers one through nine in full. Use numerals for 10 and higher.
+- Search for semicolons (;) and replace them with a period (.) For example: Instead of "This isn't needed; the system does this for you" write "This isn't needed. The system does this for you."
+- Ensure lists are parallel.
+- Avoid wordy constructions.
+- Prefer Anglo-Saxon words to Latin-based words.
+
+
+2. Clarity & Readability
+-  Write clear, concise, and short sentences that are easy to understand.
+-  Avoid jargon, colloquialisms, dialect, clipped words, and unnecessary complexity.
+-  Avoid hyperbole.
+-  Use positive formulations.
+
+3. Consistency & Tone
+-  If the audience of the text is the person who is using the product or feature, use the personal pronoun “you” and make sure the user is the center of the narrative.
+-  Use "please" when the user is asked to do something extra due to software error or if the situation is already troubling for the user. Avoid "please" when the user is asked to do something that is standard procedure.
+
+4. Inclusivity & Ethical Considerations
+-  Avoid stereotypes, discrimination, and biases.
+-  Check for stopwords, including: abort, execute, grandfather, terminate, kill, disable, whitelist, blacklist, slave, master)
+-  Output the detected stopwords as a Python list and explain why they must be replaced or avoided. If no stopwords are found, output: "Language checked."
+-  Check for potentially sensitive topics, including: personal ability, mobility, status, gender (e.g., "him", "her", "man", "woman", "girl", "boy"), sexist language, appearance, type, culture, ethnicity, language, age, economic background, religion, sexual orientation.
+-  Output the detected topics as a Python list. If no topics are found, output: "Language checked."
+-  Be mindful of verbs related to senses (e.g., see, hear, watch, listen) as they may exclude people with disabilities. Consider more inclusive alternatives where appropriate, such as:
+Instead of "See the highlighted section," → Use "Note the highlighted sections."
+Instead of "Did you hear the announcement?" → Use "Did you receive the announcement?"
+Note: "See" is ok when used to mean "refer to" → "For more information, see Troubleshooting."
+
+5. Formality & Suitability
+-  Avoid emoticons and emojis.
+- Ensure that each item of a list can stand alone and is not only understandable if you read all bulletpoints as a sentence.
+
+6. Accessibility
+Focus on content-level accessibility based on WCAG guidelines. Prioritize Level A and AA issues over Level AAA enhancements. Do not evaluate technical settings unless directly visible in the text.
+
+- **Headings**: Content must use a logical heading hierarchy. Do not use bold or enlarged text to simulate headings. Group related paragraphs under appropriate headings. For step-by-step procedures, limit to one action per step and do not group multiple actions into a single step using bullet points.
+- **Link text**: Write link text that clearly describes the destination or purpose. Avoid "click here" or "read more." Use neutral, action- or content-based wording. Avoid identical link text for different destinations on the same page.
+- **Images**: Provide alt text for all informative images. Omit alt text for purely decorative images. For charts, diagrams, or screenshots, summarize the key message rather than describing every visual detail. Do not use "shows," "displays," or "image of" in alt text.
+- **Multimedia**: If multimedia is referenced, check that transcripts are provided for audio-only content and that synchronized captions are available for video content.
+- **Instructions**: Make instructions and error messages simple and easy to follow. Clearly state input requirements. Do not rely on color, shape, position, or sensory cues alone (for example, "click the red button on the right").
+- **Plain language**: Use plain language. Write short paragraphs and sentences. Expand acronyms on first use. Use lists, images, and media only when they clarify meaning.
+- **Sensory-dependent language**: Avoid instructions that rely solely on sensory verbs such as see, read, hear, click, or look. Use "refer" or "select" instead of "see" or "click." Note: "see" is acceptable when used to mean "refer to."
+- **Color**: Ensure color is not the only method used to convey information, indicate an action, or distinguish a visual element.
+- **Tables**: Use tables for tabular data only, not for visual layout. Data tables must have clearly defined column and/or row headers. Include a brief caption or summary if the table's purpose is not obvious from the context.
+- Introduce tables, lists, images, and so on with a brief description of their purpose.
+- Make sure that sentences are complete and that images, code blocks, and so on are not in between overflowing sentences.
+
+7. Consistency
+Use the `search` tool to check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review.
+
+- **Terminology**: Identify terms, product names, or UI labels introduced or changed in the diff. Search the repo for prior uses of the old term and flag files where the wording may be inconsistent or outdated.
+- **Renamed identifiers**: When a variable, class, method, config key, or file is renamed in the diff, search the repo for references to the old name and list any files that likely need updating.
+- **Wording patterns**: If the diff establishes a new phrasing pattern (for example, a heading style, a note format, or a standard phrase), search for similar passages elsewhere in the repo that use a different pattern and flag them.
+- **Cross-references**: Check whether any links, `xref` targets, or include directives in the repo point to sections or files that have been moved or renamed in the diff.
+
+Output a list of affected files and locations for each finding. If no inconsistencies are found, output: "Consistency checked."
+
+### FINAL STEPS
+Provide a report summarizing how well the text adheres to the writing rules, highlighting issues found in each category.
+Rewrite the text to align with all guidelines while maintaining clarity, accuracy, and user focus.
+Explain each change by displaying every sentence of the revised text along with a justification for what was modified or retained.
+Make sure to not create a commit but only do the changes as explained and leave the review for a human who does the commit.

.vitepress/config.js

@@ -6,7 +6,7 @@ import { readFileSync } from 'node:fs'
 import { dirname, join, resolve } from 'node:path'
 import { fileURLToPath } from 'node:url'
 import { defineConfig } from 'vitepress'
-import languages from './languages'
+import languages from './languages/index.ts'
 import playground from './lib/cds-playground/index.js'
 import { slugify } from './lib/slugify.ts'
 import { Menu } from './menu.js'
@@ -83,7 +83,7 @@ const config = defineConfig({
 
   head: [
     ['meta', { name: 'theme-color', content: '#db8b0b' }],
-    ['meta', { 'http-equiv': 'Content-Security-Policy', content: "script-src 'self' https://www.capire-matomo.cloud.sap 'unsafe-inline' 'unsafe-eval'" }],
+    ['meta', { 'http-equiv': 'Content-Security-Policy', content: "script-src 'self' https://www.capire-matomo.cloud.sap 'unsafe-inline' 'unsafe-eval'; worker-src 'self' blob:" }],
     ['link', { rel: 'icon', href: base+'favicon.ico' }],
     ['link', { rel: 'shortcut icon', href: base+'favicon.ico' }],
     ['link', { rel: 'apple-touch-icon', sizes: '180x180', href: base+'logos/cap.png' }],
@@ -98,6 +98,15 @@ const config = defineConfig({
     build: {
       chunkSizeWarningLimit: 6000, // chunk for local search index dominates
     },
+    // cds-worker.js is constructed with `type: 'module'`; match that at build time so its
+    // dynamic import('@sap/cds') is emitted as native ESM instead of an iife require() shim
+    worker: {
+      format: 'es',
+      rolldownOptions: { output: { keepNames: true, } },
+      // Vite doesn't reuse the main `plugins` array for worker bundles; without vite-plugin-cds's
+      // node()/cap() here, the worker build misses their Node built-in shims (e.g. lazify's module.require)
+      plugins: () => [...playground.plugins()],
+    },
     css: {
       preprocessorOptions: {
         scss: {
@@ -117,7 +126,7 @@ export default config
 // -----------------------------------------------------------------------------------------------
 
 // Add rewrites
-import rewrites from './rewrites'
+import rewrites from './rewrites.js'
 config.rewrites = rewrites
 
 // Read menu from local menu.md, but only if we run standalone, not embeded as @external
@@ -132,8 +141,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: '5.0.2',
-    java_cds4j: '5.0.2',
+    java_services: '5.1.1',
+    java_cds4j: '5.1.1',
     cloud_sec_ams: '3.8.1'
   },
   gotoLinks: [],
@@ -203,10 +212,10 @@ config.themeConfig.search = {
 
 // Add custom markdown renderers...
 import { dl } from '@mdit/plugin-dl'
-import * as MdLiveCode from './lib/cds-playground/md-live-code'
-import * as MdAttrsPropagate from './lib/md-attrs-propagate'
-import * as MdDiagramSvg from './lib/md-diagram-svg'
-import * as MdTypedModels from './lib/md-typed-models'
+import * as MdLiveCode from './lib/cds-playground/md-live-code.ts'
+import * as MdAttrsPropagate from './lib/md-attrs-propagate.ts'
+import * as MdDiagramSvg from './lib/md-diagram-svg.ts'
+import * as MdTypedModels from './lib/md-typed-models.ts'
 
 config.markdown.config = md => {
   MdAttrsPropagate.install(md)
@@ -227,7 +236,7 @@ if (process.env.VITE_CAPIRE_EXTRA_ASSETS) {
 
 // Add custom buildEnd hook
 import { promises as fs } from 'node:fs'
-import * as cdsMavenSite from './lib/cds-maven-site'
+import * as cdsMavenSite from './lib/cds-maven-site.ts'
 config.buildEnd = async ({ outDir, site }) => {
   const sitemapURL = new URL(config.themeConfig.capire.siteURL.href)
   sitemapURL.pathname = join(sitemapURL.pathname, 'sitemap.xml')

.vitepress/lib/cds-playground/index.js

@@ -1,6 +1,9 @@
-import templates from './vite-plugin-templates'
+import templates from './vite-plugin-templates.ts'
 import path from 'path'
+import { dirname } from 'path'
+import { fileURLToPath } from 'node:url'
 
+const __dirname = dirname(fileURLToPath(import.meta.url))
 let enabled = false
 let plugins = () => []