Skip to content

Remove Commons Repo Workaround — Use Public npm for @sap/cds-dk and @sap/cds-mtxs - #594

Merged
akgarg06 merged 1 commit into
developfrom
RBSDMS-cds-mtxs-cds-dk-version-fix-feature
Sep 11, 2026
Merged

Remove Commons Repo Workaround — Use Public npm for @sap/cds-dk and @sap/cds-mtxs#594
akgarg06 merged 1 commit into
developfrom
RBSDMS-cds-mtxs-cds-dk-version-fix-feature

Conversation

@akgarg06

@akgarg06 akgarg06 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Describe your changes

Why

@sap/cds-mtxs@3.9.7 and @sap/cds-dk@9.9.5 (and later) are now published on public npm.
The previous workaround used SAP's internal Artifactory commons tarball URLs injected at CI runtime via secrets (SAP_CDS_MTXS_TARBALL, SAP_CDS_DK_TARBALL, NPM_AUTH_TOKEN) because these versions were not yet available publicly.
That workaround is no longer needed and has been fully removed.


What Changed

Workflow files — removed the "Setup npm registry and pin SAP tarballs" step

All five workflows that had the secret-injecting tarball setup step have been cleaned up:

Workflow Change
blackduck.yml Replaced complex tarball-inject+install step with a plain npm install --legacy-peer-deps loop
multiTenancyDeployLocal.yml Removed tarball step entirely
multiTenant_deploy_and_Integration_test.yml Removed tarball step entirely
multiTenant_deploy_and_Integration_test_LatestVersion.yml Removed tarball step entirely
cfdeploy.yml Removed tarball step from both Deploy and SnapshotDeploy jobs

The secrets SAP_CDS_MTXS_TARBALL, SAP_CDS_DK_TARBALL, and NPM_AUTH_TOKEN are no longer referenced in any workflow.

pom.xml — updated cds.install-cdsdk.version to ^9

Replaced all hardcoded exact version values with the range specifier ^9, consistent with how @sap/cds-mtxs is already declared (^3) in the Maven plugin install arguments.

File Old value New value
multi-tenant/central-space/.../pom.xml 9.8.0 ^9
multi-tenant/personal-space/.../pom.xml 9.3.1 ^9
single-tenant/central-space/demoapp/pom.xml 8.0.2 ^9
single-tenant/personal-space/demoapp/pom.xml 8.0.2 ^9

The srv/pom.xml install arguments already used @sap/cds-mtxs@^3 and remain unchanged. With cds.install-cdsdk.version=^9, the full install command becomes:

npm install @sap/cds-dk@^9 @sap/cds-mtxs@^3 --no-save

package.json files — no change needed

All four multi-tenant package.json files already declare "@sap/cds-dk": "^9" and "@sap/cds-mtxs": "^3". These are correct and unchanged.

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.

Comment thread .github/workflows/blackduck.yml
@akgarg06
akgarg06 merged commit ac78725 into develop Sep 11, 2026
9 checks passed
@akgarg06
akgarg06 deleted the RBSDMS-cds-mtxs-cds-dk-version-fix-feature branch September 11, 2026 09:55
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.

3 participants