Hahn-Solo Product Management
  • Dashboard
  • Technologies
  • Competitors
  • Tasks
Theme
Basic Information
Status
Open
Priority
Next
Category
Version Update
Repo
SCB PM
Effort
Trivial
Task ID
T-D8094B9C
Details
Upgrade @sitecore-cloudsdk Packages to Latest
The `basic-nextjs` and `basic-nextjs-pages-router` starters pin `@sitecore-cloudsdk/core` and `@sitecore-cloudsdk/events` at `^0.5.1`, while the kit starters use `^0.5.4`. Align all starters to the latest `0.5.x` release. Verify compatibility with Content SDK v2.0.1 when that upgrade lands.
Why
Version drift within the same monorepo creates inconsistent behavior between starters. Developers choosing between starters may encounter different CloudSDK behavior.
Evidence
basic-nextjs `package.json` vs kit starter `package.json`
Details
Context: The `basic-nextjs` starter pins `@sitecore-cloudsdk/core` and `@sitecore-cloudsdk/events` at `^0.5.1`, while the kit starters use `^0.5.4`. This minor drift means starters within the same repository may exhibit different CloudSDK behavior. The drift should be resolved before the Content SDK v2 upgrade to reduce variables.

Steps:
1. In `examples/basic-nextjs/package.json`, update `@sitecore-cloudsdk/core` and `@sitecore-cloudsdk/events` from `^0.5.1` to `^0.5.4`.
2. In `examples/basic-nextjs-pages-router/package.json`, make the same update.
3. Run `npm install` and `npm test` in both starters.

Acceptance criteria:
All starters reference the same `@sitecore-cloudsdk/*` version range
No behavioral regressions in CloudSDK-dependent features

Risks: None identified.
Source Report
reports/product-management/scb/2026-04-05-scb-pm.md
Report date: Apr 5, 2026