Skip to content

Upgrade @sap/cds-dk and cds.services.version Across All Sample Apps - #596

Merged
akgarg06 merged 8 commits into
developfrom
RBSDMS-multi-prs-feature
Sep 11, 2026
Merged

Upgrade @sap/cds-dk and cds.services.version Across All Sample Apps#596
akgarg06 merged 8 commits into
developfrom
RBSDMS-multi-prs-feature

Conversation

@akgarg06

@akgarg06 akgarg06 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Describe your changes

  • @sap/cds-dk was pinned to stale exact versions (8.0.2, 9.3.1, 9.8.0) across different apps, causing version drift between single-tenant and multi-tenant apps.
  • Single-tenant apps were on cds-dk@8 and cds.services.version 4.1.1, while multi-tenant was already on cds-dk@9 and cds.services.version 4.3.0.
  • Standardising all apps to the same major version range (^9) and services runtime (4.3.0) removes that drift and ensures consistent behaviour across all integration tests.

What Changed

cds.services.version — updated to 4.3.0 for single-tenant apps

Single-tenant apps were on 4.1.1 while multi-tenant was already on 4.3.0. The mismatch caused integration test failures (403001 authorization errors, draft operation failures) after upgrading cds-dk from 8 to ^9. Aligning to 4.3.0 fixes this.

File Old New
single-tenant/central-space/demoapp/pom.xml 4.1.1 4.3.0
single-tenant/personal-space/demoapp/pom.xml 4.1.1 4.3.0
single-tenant/personal-space-2/demoapp/pom.xml 4.1.1 4.3.0
single-tenant/personal-space-3/demoapp/pom.xml 4.1.1 4.3.0

Multi-tenant cds.services.version was already 4.3.0 — unchanged.


Version Alignment After This PR

App cds.services.version cds.install-cdsdk.version
multi-tenant (central + personal) 4.3.0 ^9
single-tenant (all 4 apps) 4.3.0 ^9

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Checklist before requesting a review

  • I follow Java Development Guidelines for SAP
  • I have tested the functionality on my cloud environment.
  • I have provided sufficient automated/ unit tests for the code.
  • I have increased or maintained the test coverage.
  • I have ran integration tests on my cloud environment.
  • I have validated blackduck portal for any vulnerability after my commit.

Multi Tenant : https://github.com/cap-java/sdm/actions/runs/34585487862
Single Tenant : https://github.com/cap-java/sdm/actions/runs/34595452598

Upgrades @sap/approuter from 16.8.2 to 23.0.0 across all four app spaces
(multi-tenant central/personal, single-tenant central/personal) to address
security vulnerabilities.
…jackson-core

- Bumps jackson-databind from 2.18.9 to 2.22.2
- Bumps jackson-core from 2.18.6 to 2.22.2
- Adds jackson-annotations 2.22 as an explicit dependency
- Bumps httpclient5 from 5.4.4 to 5.6.4
…sap/cds-mtxs

@sap/cds-mtxs@3.9.7 and @sap/cds-dk@9.9.5 are now available on public npm,
so the CI workaround that injected SAP Artifactory tarball URLs via secrets
(SAP_CDS_MTXS_TARBALL, SAP_CDS_DK_TARBALL, NPM_AUTH_TOKEN) is no longer needed.

- Removes the "Setup npm registry and pin SAP tarballs" step from all five workflows
- Replaces complex tarball-inject+install in blackduck.yml with plain npm install --legacy-peer-deps
- Updates cds.install-cdsdk.version to ^9 in all four pom.xml files
@akgarg06 akgarg06 changed the title Rbsdms multi prs feature Upgrade @sap/cds-dk and cds.services.version Across All Sample Apps Sep 11, 2026
@akgarg06
akgarg06 merged commit 79e9af0 into develop Sep 11, 2026
9 checks passed
@akgarg06
akgarg06 deleted the RBSDMS-multi-prs-feature branch September 11, 2026 12:26
@akgarg06
akgarg06 restored the RBSDMS-multi-prs-feature branch September 11, 2026 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants