chore(deps): bump @decocms/start to 5.3.0-rc.2#50
Merged
Conversation
5.3.0-rc.0 (currently pinned) and 5.3.0-rc.1 were both deprecated upstream because they carried PR #164's framework-agnostic-entrypoints refactor, which duplicated module-level state across bundled entries (loaders 404'd, direct-POST observability channels no-op'd). Upstream reverted on main (@decocms/start@5.2.2) and re-applied the o11y stack on the src/-exports baseline as 5.3.0-rc.2. Substantive deltas the o11y operations work in this branch depends on (createVtexFetch / createShopifyFetch / fetchWithCache wiring) are preserved in rc.2 — the o11y API surface (instrumentWorker, withTracing, recordCacheMetric, injectTraceContext, createOtlpHttpMeterAdapter, createOtlpHttpErrorLogAdapter) is identical between rc.0 and rc.2. Typecheck + 413 vitest tests pass against rc.2. Drops the `next: >=15.0.0` peer (Next.js entrypoint was reverted from @decocms/start). apps-start never imported from @decocms/start/next so no source changes needed. Co-authored-by: Cursor <cursoragent@cursor.com>
vibe-dex
added a commit
that referenced
this pull request
May 19, 2026
PR #50 (chore(deps): bump @decocms/start to 5.3.0-rc.2) shipped with a truncated lockfile produced via `npm install --legacy-peer-deps`. The legacy-peer-deps flag was a workaround for a local registry config issue (a global npmrc pointing at npm.pkg.github.com/bawclothing/ was intercepting public-package fetches), not because of a real peer-dep conflict. The truncated lockfile passed local `npm test` (which doesn't require a complete tree for resolved test deps) but blocked the Release workflow's `npm ci` — strict-frozen install that fails on any missing transitive package — so semantic-release never ran and 1.15.0-next.2 was not cut. This commit regenerates the lockfile with the public registry forced (`npm_config_registry=https://registry.npmjs.org/ npm install`), restoring 504 packages and the full transitive tree. typecheck + 413 vitest tests pass against rc.2. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps `@decocms/start` from the deprecated `5.3.0-rc.0` to `5.3.0-rc.2` (the o11y stack rebased onto the post-revert main).
Brings the operations work on this branch (createVtexFetch / createShopifyFetch / fetchWithCache wiring) onto a non-broken framework foundation. Both rc.0 and rc.1 were npm-deprecated upstream after PR #164's framework-agnostic-entrypoints refactor was reverted in decocms/deco-start#181 (loaders 404'd, direct-POST observability silently no-op'd).
Notes
Validation
What this enables
Lockfile churn
The `package-lock.json` diff is large because npm re-resolved peer-deps when bumping. Spot-checked: the only intentional version change is `@decocms/start: 5.3.0-rc.0 → 5.3.0-rc.2`. Other "removals" are npm consolidating duplicated transitive trees.
Made with Cursor
Summary by cubic
Bump
@decocms/startfrom5.3.0-rc.0to5.3.0-rc.2to replace deprecated builds and fix framework regressions (loader 404s, no-op direct-POST observability). The o11y API is unchanged; no source changes needed.peerDependenciesanddevDependenciesto@decocms/start@5.3.0-rc.2.rc.2removes thenextpeer; this repo does not use@decocms/start/next.Written for commit 62dc4a4. Summary will update on new commits. Review in cubic