capire

Appearance

Description ​

CDS 10 removes the compatibility path that allowed the MTX sidecar (@sap/cds-mtxs) to operate alongside a main application still running @sap/cds below version 9.7. Projects using multitenancy with an MTX sidecar must ensure the sidecar's @sap/cds dependency is at 9.7 or above before upgrading the main application to CDS 10. Upgrading the main application without upgrading the sidecar first may result in deployment or runtime errors in the multitenancy workflows (subscription, tenant upgrade, metadata synchronization).

How to Check ​

  • [ ] Check the project's package.json for @sap/cds-mtxs — if absent, this entry does not apply.
  • [ ] If @sap/cds-mtxs is present, check the sidecar's own package.json (typically in a mtx/sidecar/ subdirectory) for the @sap/cds version.
  • [ ] Confirm that @sap/cds in the sidecar package is >= 9.7.0.
  • [ ] Check mta.yaml or deployment descriptors for separate sidecar module declarations that may pin older @sap/cds versions.

Migration Steps ​

  1. Upgrade the MTX sidecar's @sap/cds dependency to >= 9.7 before upgrading the main application to CDS 10:

    diff
    // mtx/sidecar/package.json
{
  "dependencies": {
-   "@sap/cds": "^9.0.0",
+   "@sap/cds": "^9.7.0",
    "@sap/cds-mtxs": "^2.0.0"
  }
}

  2. Run npm install in the sidecar directory and verify it starts correctly with the updated @sap/cds version before upgrading the main application.

  3. After confirming the sidecar is on >= 9.7, upgrade the main application to CDS 10:

    diff
    // package.json (main app)
{
  "dependencies": {
-   "@sap/cds": "^9.7.0",
+   "@sap/cds": "^10.0.0"
  }
}

  4. Deploy the upgraded sidecar before or simultaneously with the main application.

Notes ​

The upgrade sequence matters: the sidecar must be at >= 9.7 before the main application moves to CDS 10. Check the @sap/cds-mtxs release notes for any additional compatibility requirements with CDS 10.